Join Atlassian’s Early Access Program for Priorities per Project in Jira Cloud

[#1]

Hi everyone,

We’re enabling Jira admins to set up priority schemes in Jira Cloud. This means you can use different priorities for different projects. We’re looking for Jira admins to join our Early Access Program (EAP) and give us feedback on this feature.

See the below table for details:

What will be available?	By default, all the priorities you have today will be in a default priority scheme for all existing projects. You can: Add or remove priorities in the default priority scheme. Create your own custom priority schemes for specific projects. Edit or delete priority schemes. Manage priority schemes in Jira settings. Note: We’re not enabling interactions via APIs.
What do you need to do to sign up?	Fill in the EAP survey. Note: If you’re not a Jira admin and you think this will benefit your team, speak with your admin to get involved.
For any questions and clarification	Reply to this post for questions about the survey or email me directly on            nschwartz@atlassian.com. If you qualify, you will be invited to a private community group for this EAP where you can post questions in the group and we’ll get back to you.
What will happen to the feature after the EAP?	You can continue to use this feature on your instance. We can enable this feature for production instances if you’re testing on a sandbox as well.

Ready to go? Fill in the EAP survey.

Note: Features in the EAP may have some bugs. We’ll share more details about these bugs, and you can also raise them in the group.

Regards,

Nicole

[Kristján Geir Mathiesen]

That is very...

Look forward to participate in the EAP.

[Nicole Schwartz]

Love the enthusiasm @Kristján Geir Mathiesenthank you!

[Hassan Shahin]

Hi,

I just need to ensure I am getting this right.

Is this feature about having different priorities schemes to be applied to the tickets in the same project, or is it having different schemes to be applied to multiple projects (but not their enclosed tickets)

Thanks

[Bogdan Gorka]

@Hassan Shahin 

I think (and I hope) that this is about bringing the standard Jira Server/DC functionality where you can have different sets of priorities associated with different Jira projects.

For example:

in project A you can have:

• Low, Medium, High, Highest

and in project B you can have

• Low, High, Blocker

[Nicole Schwartz]

Hey @Hassan Shahinyes @Bogdan Gorka is correct - thanks for answering this!

This feature is about associating priority schemes to different projects. A Jira admin can create a priority scheme include a subset of the globally available priorities and associate that scheme with different projects. This means that you can have different priorities for different projects.

[Hassan Shahin]

Thanks @Bogdan Gorka and @Nicole Schwartz 

[Bogdan Gorka]

@Nicole Schwartz I thought I would let you know, just in case, that once you deploy this long awaited change in the Cloud then remember to update the course 'Jira Governance and Housekeeping' for ASB-116.

Please see the screenshot from this course. After your feature deployment, this answer will not be valid any more.

[Dan Tombs]

The long awaited missing scheme from server is coming to cloud!!!!

[Nicole Schwartz]

@Bogdan Gorkathanks for letting us know!

Appreciate the excitement, @Dan Tombs