Cross-team Ticket Priority Requirement

[Christoff Jiang]

Can we change the setting of Jira so a cross-team ticket must be in a certain priority?

Our company requires that a cross team ticket must be in Highest or High Priority. Currently, we need to manually go through all the tickets to check the priority for all corss-team tickets, which takes a lot of time.

Is it possible to change some setting so the ticket creator can only set the priority to Highest or High when assigning a ticket to a cross-team member in the first place?

[Trudy Claspill]

Hello @Christoff Jiang 

Welcome to the Atlassian community.

How would Jira be able to identify that a ticket is being assigned to a cross-team member?

When is the ticket assigned to a cross-team member? Does that only happen during the creation of the issue, or might it happen after the issue has been created?

There might be a couple of methods to address this, but it depends on the answers to those two questions.

[Christoff Jiang]

Thank you so much for replying!

We use the Project field to distinguish between different team. Please allow me to elaborate the process using the following example.

When someone is creating a ticket, let's assume assignee A belongs to project X, reporter R belongs to project Y. A cross team ticket defined when X does not equal to Y.

This may happen when the issued being created or after its creation. After this issue is created, the priority should not be able to be changed to any priority lower than High. However, if the change in reporter R or change in Assignee A result in they belongs to the same project, changing it to lower priority can be allowed.

Thank you again fro looking at this case. 

[Trudy Claspill]

How exactly do you know that a given user "belongs" to a project?