|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Bill Schneider - 15/Mar/07 10:02 AM
If multiple people can be in a project role, how would one assignee be chosen?
That is a problem and requires some rework on the Assignee part, to also hold a Role as an assignee. But we would welcome this functionality very much. We currently work around this limitation, by having dummy users calles "any_analyst", "any_developer", etc. That's obviously far from ideal.
I am with Bill on this one.
If the role has more than one member, who do we assign the issue to? This would be a very nice feature. Currently another option seems to make a workflow for every project with specific people selected to act as the various lead roles.
With multiple people allowed within a role you'd have to do a little extra work. I see a couple of options. If there are other workarounds to get this same type of functionality in 3.8 please feel free to share them. This might be a workaround for some people...
I have just started using two different plugins to achieve something like this.
I then created a custom field for each of the roles and placed them on an "Assignments" tab on the primary issue screen. My workflow is pretty involved, such that the user executing a particular transition can be safely assumed to be in a particular role. I can then immediatly assign the issue to the user who executed the transition as well, although that post function seems to have to come after "Update change history for an issue and store the issue in the database" in order to take effect. In that case I am assigning the user from the custom field I just stored his/her username to. If the issue moves "backward" in the workflow, it is also possible for me to assign it to the appropriate person for review, based on who executed certain transitions. I don't imagine this will be a great workaround for everyone...but so far it's improving the utility of the app for me, even if it is a hack. Very much appreciated. This way we could have a role responsible for qualifying the incoming issues. Today we solve that by having a dummy user called inbox.<customername> and we then poll this inbox.
I have created a plugin that addresses this issue. Can you pls try http://confluence.atlassian.com/display/JIRAEXT/Assign+To+Role+Member+workflow+function
 and let me know if it works for you? Another way to approach this is to allow a selection of a Lead for each role as mentioned in JRA-13680.
Guys - any news from the field?
As a temporary workaround, we had to hardcode the assignee names into certain transitions (via "Update issue field" post-function) which's really a time bomb, and it will blast the process when a new Lead is hired. One could consider a validator function to prompt the user if more then 1 user is acting in the dedicated role prior to going into the post. It probably only requires to remember the selected role member and pass it to the post function (e.g. use of a hidden field?). Has anyone done some work on this given there are some similar plugins making the round?
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Add "Assign to Role Member" workflow post-function
