|
[
Permlink
| « Hide
]
Philip Soffer added a comment - 02/Nov/05 01:04 PM
The usefulness is more than occasional in my world. If there is a new feature request, that needs to go through a different workflow than a bug fix, starting wtih it being assigned to a product manager rather than to a dev lead. I'm just getting started with Jira, so I'm sure there are other ways to do this, but it would have been intuitive for me to do it this way.
Hi Philip,
If you are using Jira Enterprise, you can set up different workflows for each issue type. In these workflows it is also possible to automatically assign an issue to a particular user, through the use of a post function Once you have created your new workflow information associating the workflow to an issue type can be found here: http://www.atlassian.com/software/jira/docs/latest/activating_workflow.html If you have any further questions, email us at jira-support@atlassian.com Thanks, When the option to "Allow unassigned issues" is set to "OFF", the default assignee is the project lead or (for components with a seperate default assignee) the component lead.
But it should be possible to specify a different default assignee than the project lead on the "Edit Project" page, which is especially useful for issues which do not belong to a certain component and then would be assigned to the project lead (but that is not what i want). Same in my company. We have, like Jira, an issue type "Support Request" where we'd like the default assignee to be our support department.
Best Regards I add my support to this request... It would be very helpful to us if we could specify any valid Jira User who is attached to the project as the default assignee when setting up the project in Jira. The restriction to project lead or no-one is counter-productive for us.
I also add my support to this request. Like Andrew Hurst, we would like a default assignee for the support department and cannot do this at the moment.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||