History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-5265
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Robert Greig
Votes: 2
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Allow Issue Settings to be project specific

Created: 18/Nov/04 05:17 AM   Updated: 19/Nov/04 12:29 AM
Component/s: Backend / Domain Model
Affects Version/s: 3.0.2
Fix Version/s: None

Time Tracking:
Not Specified

Environment: Any
Issue Links:
Duplicate
 

Participants: Jeff Turner [Atlassian] and Robert Greig
Since last comment: 192 weeks ago
Resolution Date: 19/Nov/04 12:29 AM
Labels:


 Description  « Hide
We are planning on hosting a large number of projects on our Jira instance.

These projects will often require different issue types, priorities, resolutions and statuses.

I think it therefore makes sense to make an "issue settings scheme" concept just like permission schemes, workflows etc.

Unless I am missing something and this is already possible?



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jeff Turner [Atlassian] - 19/Nov/04 12:29 AM
Yes, it would be the next logical step. Per-project issue types is now our most popular issue (JRA-1602). We're tracking the general feature request in JRA-3821.