Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Unresolved
Fix Version/s: None
Component/s: Administration - Others
Labels:
- affects-server
- jw-core

UIS:
116
Support reference count:
6
Current Status:

Hide

Atlassian Update – 16 April 2019

Hi everyone,

We've reviewed this suggestion again and it remains a potential addition to our longer-term roadmap. This is not yet part of our plans for the nearest 6-12 months. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap.

To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

To read about our recent investments, please check out this community post on bringing more visibility into what's coming in Jira Server and Data Center

Kind regards,
Jira Server Product Management

Show
Atlassian Update – 16 April 2019 Hi everyone, We've reviewed this suggestion again and it remains a potential addition to our longer-term roadmap. This is not yet part of our plans for the nearest 6-12 months. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap. To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . To read about our recent investments, please check out this community post on bringing more visibility into what's coming in Jira Server and Data Center Kind regards, Jira Server Product Management
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

This suggestion has been separated from JRASERVER-3821 as a separate feature request which we'll prioritise independently. We will use all the comments around resolutions from the original suggestion (JRASERVER-3821) in the design of the feature, so no need to put the same comments, just make sure to vote and watch the issue! We will provide further updates in here.

Original Request

As a JIRA Administrator I need more granular configuration for my projects.

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

image-2018-02-21-18-50-47-026.png
52 kB
21/Feb/2018 5:50 PM

Issue Links

derived from

JRASERVER-3821 Priorities per Project and Resolutions per Issue Type

Closed

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(4 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Jakub Lazinski (Inactive)

Votes:: 694 Vote for this issue

Watchers:: 377 Start watching this issue

Dates

Created:: 07/Sep/2017 3:02 PM

Updated:: 14 hours ago