New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-13680
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Nikolay Gorbunov
Votes: 2
Watchers: 3
Operations

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

Enable auto-assigning to Group Lead

Created: 04/Oct/07 06:24 AM   Updated: 04/Oct/07 09:57 PM
Component/s: Roles
Affects Version/s: 3.8
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Nikolay Gorbunov
Since last comment: 47 weeks, 1 day ago
Labels:


 Description  « Hide
Currently, JIRA does not support a "Lead" status within a Group. This is weird because when an issue gets to a certain state, it often has to be auto-assigned the The Guy In Charge first who will decide what to do next. (E.g. if an issue gets to "To Be Regressed", it should be assigned to QA Lead first (automatically), and then reassigned by the lead to a particular resource.)

What would be nice to have from this standpoint is:

  • Capability to define a "Default Member" / "Lead" of a Group
  • A post-function to auto-assign issue to a Lead of specified Group (selected from a dropdown list)

The "Assign to Group" plugin does not qualify because it requires explicitly specifying the Group Lead in transition properties which's a maintenance problem. Defining users and groups must be located entirely in User Management section, else evey time a group lead is hired/fired, the admin would have to swicth workflows (which may take up to hours if the databse is big enough) and modify every certain transition to change the user defined there.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.