-
Type:
Suggestion
-
Status: Under Consideration (View Workflow)
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: System Administration
-
Feedback Policy:
-
UIS:154
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. I’m Nathan a Product Manager at Atlassian that is working on project configuration for next-gen projects.
We have been working hard on simplifying project setup and configuration, as one of the Jira team's top priorities right now. We are making a big investment to make project configuration in Jira so intuitive, that anyone can do it. This is no small feat, given that we need to retain the power and configurability that our users expect.
To do this we have been iteratively working on next-gen projects (formally known as Agility projects), starting with a simple experience and adding more powerful features as we go. I have been eagerly watching top voted feature request tickets like this for sometime and waiting for the opportunity to work on this feature. I wanted to update everyone to say that my team is actively envisioning what priorities and resolutions per project will look like in next-gen projects.
Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Nathan Sturgess
nsturgess@atlassian.com
Product Manager, JIRA Platform
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.
- Customizing velocity templates to limit the visible priorities and resolutions per project, similar to what's posted below (though this approach does not apply for JIRA Cloud customers).
- duplicates
-
- Resolved
-
- Resolved
-
- Gathering Interest
- is duplicated by
-
CLOUD-6553 Create schemes for Priorities
-
- Closed
-
-
-
- Closed
-
-
- Resolved
-
- Resolved
-
- Resolved
-
- Resolved
- is related to
-
- Open
-
- Resolved
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
1.
|
Create Admin screen for Priority Scheme |
|
Resolved | Unassigned |
2.
|
Apply those velocity templates, but get config from the data-source |
|
Resolved | Unassigned |
