Details
-
Suggestion
-
Resolution: Unresolved
-
15,961
-
660
-
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
We’re very happy to share that we’re starting our general availability release next week! We’ve now closed the EAP and will be gradually rolling out this experience over the next few weeks.
Thank you for all your continued interest on this ticket and we’re excited to deliver this feature and resolve this request for you all!
Regards,
Nicole
—
November 2023
Hi everyone,
We’re now tracking to an estimate of early 2024 for our general availability launch as it’s taking us more time than we expected. We’re continuing to offer our Early Access Program (EAP) and we now have support for migration with Jira Cloud Migration Assistant (JCMA) so you can sign up for our EAP to use your priority schemes from Server/Data Center in Cloud.
We’ll update you with more details on our general availability release when we’re ready. Thank you for your continued interest and engagement with this ticket.
Regards,
Nicole
—
October 2023
Hi all,
We’re a month into our Early Access Program (EAP) and it’s still open if you’d like to be involved! Please see our community post here for more details on the EAP and how to get involved.
We’ve been collating feedback from the EAP and working towards our General Availability release by the end of this year. We’ll provide more details as we progress.
Regards,
Nicole
—
August 2023
Hi everyone,
We’re excited to share that we’re close to launching our Early Access Program (EAP). We’d love for you to be a part of it and give us feedback on this feature. Please see our community post here for more details on the EAP and how to get involved.
Regards,
Nicole
—
July 2023
Hi all,
We’ve made good progress towards an Early Access Program in late September 2023 and will provide more details on how to be involved in the next couple of months as we progress. We’re really excited to be working on this and thank you for your continued interest and patience.
Regards,
Nicole & the Atlassian team
—
May 2023
Hi everyone,
We’ve wrapped up the customer research study which was very insightful and thanks for everyone’s continued interest and valuable feedback on this ticket.
We’ve also completed our technical investigations and will start implementation this month. We’ll be working towards an Early Access Program and will provide more details when we are ready.
Please feel free to reach out with any questions.
Regards,
Nicole & the Atlassian team
—
April 2023
Hi everyone,
We are doing further research on this topic and would love to invite you to take part in an upcoming customer research study!
What’s involved in the research:
- Sessions are 1 hour and conducted over video-conference, so you can participate from anywhere around the globe.
- During the research, we'll start with a general chat to get to know you, then, you might explore a prototype and complete some tasks.
- As a token of our appreciation, you'll receive an e-gift card within 5 days of completing your session.
If you're interested in taking part, please complete this survey and we will get back to you. We’re testing with a small group to begin with and there will be chances to give more feedback in the future.
If you have any other questions at all, please email me directly on nschwartz@atlassian.com. We look forward to meeting you!
Regards,
Nicole & the Atlassian team
—
February 2023
Hi everyone,
As mentioned previously, we have now started onboarding a team (in Q1) to work on Priorities per Project, and have started analysis and early technical investigations. We are currently aiming to have high level estimations and timelines by the end of March. We appreciate your patience, and as the team ramps up, we will be able to provide updates more regularly.
Finally, we’re also planning to hold research sessions in March - so please join our focus group (see details below) if you are interested to participate.
Regards
Carol & the Atlassian team
—
November 2022
Hi everyone,
Thank you for your continued interest, insightful feedback, and votes on this ticket. We apologize for the lack of update on this as we’ve been focussed on ensuring our cloud environment is performant at scale.
To track the progress of this ticket more effectively, we’re updating this ticket to be "Priorities per project" and created a new ticket: JRACLOUD-80093 (Resolution per Issue Type) to track it as a separate feature. We are marking Priorities per project as our first focus from what we’ve heard from you through the comments you’ve shared, and will move it to “In Progress”. We’ll continue monitoring the interest for Resolutions per Issue Type.
Update on Priorities per Project:
As part of a larger initiative to improve the way fields can be configured, we are planning to bring the ability to configure field contexts for Priority, Description, and potentially other system fields. We believe this unlocks multiple use cases we’ve heard from you - e.g. allowing for different default priorities per issue type, multiple contexts for custom fields per project, default values for description fields.
These fields are core in Jira and we will be spending time to make sure the changes we make carry through all experiences in Jira smoothly. We have started planning and design work for this and will be onboarding a team to work on it from Q1 next year, and I will provide periodical updates on this ticket.
For customers migrating from Server, we will look into providing a migration pathway from data in Priority schemes to field contexts.
While we’re building this ability for you to have more control over key fields, we welcome you to join our focus group and work with us to improve configuration experiences in Jira. If you are interested, please email me at clow@atlassian.com and I’ll share more details on the group.
Please feel free to reach out with any questions.
Regards
Carol & the Atlassian team
Regards,
Carol
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.
Attachments
Issue Links
- 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...
1.
|
Create Admin screen for Priority Scheme | Closed | Unassigned | |
2.
|
Apply those velocity templates, but get config from the data-source | Closed | Unassigned |