/
Next-Gen Project Specifics

Next-Gen Project Specifics

Atlassian has launched the ability to re-use the global custom fields in the next-gen (Team-managed) projects. Now you could add the custom fields to your next-gen project and use the full capability of the Smart Checklist šŸŽ‰

Hereā€™s how Atlassian describes it:

Team-managed projects, as its name suggests, empowers teams to configure their own projects to suit how they work. With this new feature, project admins now have the ability to re-use custom fields that are provided and managed by their Jira admins, saving them time to keep field configuration in sync across projects.

Furthermore, downstream applications, like Automation or other reporting processes will no longer require additional data cleansing or logic to merge duplicate fields across projects.

Ā 

What has changed?

Now, you could add ā€œChecklistā€œ and ā€œSmart Checklistā€œ custom fields to the team-managed projects.

With a set up of ā€œChecklistā€œ custom field you could:

With a set up of ā€œSmart Checklistā€œ custom field you coud:

Whatā€™s missing?

Validate before transition

Workflow customization isn't available yet for Next-Gen projects. As of now, it is on the longer-term roadmap of theĀ Atlassian team. Herein, transition validators are not available either.

Track checklist progress on Agile Board

Fields customization on Agile Board isnā€™t available yet for Next-Gen projects. You could track the status of this feature on the Atlassian backlog.

Ā 

We're keeping an eye on next-gen projects development, and will be updating our documentation when new features influencing Smart Checklist add-on work to arrive.Ā 

Feel freeĀ to track the recently shipped and coming-soon features of Next-Gen projects as wellĀ here.Ā 

Related content