[#JRA-9331] Add a 'Version Lead'

JIRA

Add a 'Version Lead'

Created: 10/Feb/06 06:53 AM Updated: 15/Oct/07 11:13 PM

Component/s:

Project Management

Affects Version/s:

3.4.2

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

~~JRA-4752~~ Project roles

Participants:	Michael Phillimore-Brown and Nikolay Gorbunov
Since last comment:	41 weeks, 3 days ago
Labels:

Description

« Hide

Suppose you had different people in charge of Jira 3.4 and 3.5 and wanted them to be notified of changes to issues relating to their project. Currently I don't think this is possible.

I would like to see a 'Version Lead' functionality that closely mirrors the 'Component Lead' idea, where we can put somebody in charge of each version. That way they could be notified of changes, given permissions only to that version etc.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Nikolay Gorbunov - 04/Oct/07 04:32 AM

+1. In our company, every version has a dedicated manager who's in charge of all issues affecting it, and an issue is often first assigned to "version lead" depending on version it affects. Would be nice to have:

A Lead associated with every Version, maintainable from Manage Versions
A post-function capable of assigning the issue to Version Lead, version being defined by a generic or custom field