-
Suggestion
-
Resolution: Fixed
-
12,162
-
667
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hey everyone,
We're pleased to announce that Priority Schemes is now live on Jira Cloud! You can read all about it here.
If you are on bundled release tracks you can expect to see it with part of the next bundle coming to you on 11th June.
Please feel free to send any feedback our way through the community post linked above, we would love to hear from you!
We are continuing to track the feature request for resolutions per issue type here.
Regards,
Carol, Nicole and the team at Atlassian
Original request description:
As a JIRA Administrator I need more granular configuration for my projects:
- I want to be able to specify different priorities for different projects instead of having a global priority list. The current global priority can be used as a default, but I would like to be able to change them per project.
- Depending on the issue type, the resolution may be different. For example: in case of bugs, the resolution may be set to "fixed", but in case of improvements there is nothing to fix and the resolution should rather be "implemented". I need to be able to specify the default resolution separately per each issue type.
Potential Workarounds:
There are some workarounds that can provide some solutions to this issue:
- Custom fields for priorities and resolutions can be used on a per-project basis.
- duplicates
-
JRACLOUD-1871 Custom Issue Types + scope
- Closed
-
JRACLOUD-32049 Individual priorities for every project
- Closed
-
JRACLOUD-44150 Possibility to make different priorities for different projects
- Closed
-
JSDCLOUD-3400 Allow for Service Desk to use it's own priority schema while not impacting Jira's Priorities
- Closed
- is duplicated by
-
JRACLOUD-25910 There should be more configurations which can be adjusted by projects - For example: Time Tracking, Resolution and Priority.
- Closed
-
JRACLOUD-35598 As an Administrator, I would like to set up resolution schemes
- Closed
-
JRACLOUD-42890 Allow different resolutions for different projects
- Closed
-
JRACLOUD-62903 Configure Priority based on Project
- Closed
-
CLOUD-6553 Create schemes for Priorities
- Closed
-
CLOUD-6554 Create schemes for Resolutions
- Closed
-
JSWCLOUD-21455 Build Priority Schemes for Jira Cloud
- Gathering Interest
-
ENT-995 Loading...
- is related to
-
JRACLOUD-16443 Create a jira.field.resolution.include transition attribute
- Closed
-
JRASERVER-3821 Priorities per Project and Resolutions per Issue Type
- Closed
-
JSDCLOUD-3400 Allow for Service Desk to use it's own priority schema while not impacting Jira's Priorities
- Closed
-
JSDCLOUD-1374 Priorities per Service Desk project
- Gathering Interest
-
ENT-346 Loading...
- relates to
-
JRACLOUD-83492 Permission and Priority scheme changed with no audit log entries
- Closed
-
MOVE-9460 Loading...
-
MOVE-131600 Loading...
- split to
-
JRACLOUD-80093 Resolution per Issue Type
- Under Consideration
- is resolved by
-
ENT-207 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...