[#JRA-5453] Resolutions per project / issue type

JIRA

Resolutions per project / issue type

Created: 07/Dec/04 05:10 PM Updated: 24/Oct/05 12:51 AM

Component/s:

Backend / Domain Model

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

JRA-3821 Priorities, Resolutions and Statuses per project / issue type

This issue is duplicated by:

~~JRA-5856~~ Resolution type and Issue type by project

Participants:	Andrés Pedrera, Jeff Turner [Atlassian] and Nick Menere [Atlassian]
Since last comment:	143 weeks, 2 days ago
Resolution Date:	24/Oct/05 12:51 AM
Labels:

Description

« Hide

Often, issues of different types or in different projects have different sets of possible resolutions. Eg., a 'support request' issue may have the resolution 'resolved locally', which does not make sense for genuine product bugs.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Andrés Pedrera - 24/Feb/05 08:20 AM

This is exactly the same problem that we have in my company. We need different resolution schemes for every project, so it would be nice news to know that it will be posible in next release of Jira.

[ Permlink | « Hide ]

Nick Menere [Atlassian] - 24/Oct/05 12:51 AM

Am closing this issue as a duplicate of JRA-3821 as it has more votes and watches.

Cheers,
Nick