|
[
Permlink
| « Hide
]
Ben Jones added a comment - 18/Sep/06 07:56 PM
I have had 2 customer's request this functionality within the last 2 weeks. Any chance this might be looked at in future versions?
We are having this same problem. We would love to use Jira as a change management system, but we need flexible workflow.
We need a workflow transition that remembers (during this open cycle i.e resets if ticket is reponed etc) the approvers that have approved at this step and does not transition to the next step until a number approvers have approved. Also we would need the transition that handles the decline route. For example we have 4 people that handle our network change system (in Sharepoint If this could be done, then Jira would become an instant hit. Darren,
1. have you investigated subtasks? 2. Also you may be able to implement this functionality as a condition in combination with a customfield "approvals". The condition would check, whether there are three approvals in the customfield. I'd go with #1... Hth, Stefan,
We've tried sub tasks, but that doesn't quite work. We want to enter an issue and then start the workflow by clicking "Request Approval". An email would then be sent to those people that need to approve decline this issue. These people could be in a project role "Approvers" for the project which you set when you design the work flow action. How these would get recorded, I'm not sure, but probably a custom field "Approved By" and another "Rejected By". When so many approvers have approved, the issue moves on to the next step in the work flow emailing people that the issue has been approved/declined. Another thought is that when someone starts the work flow, the assignee could be set to the project role. I know there is an issue for this to allow issues to be assigned to groups. This would be quite nice. -darren Darren,
to do that, you may -Stefan Why is this one such a low priority? This is a feature that my company really want. We need to be able to have signoffs using different sets of users that changes per ticket.
I agree that the priority should be raised on this
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Minor
Add an improvement to workflow to allow multiple users to approve an issue in any order
) and we need 3 out of four of them to have approved an issue before it carries on. We could have a transition that you could link to a project role and specify how many need to approve (the inverse would work for decline, therefor we don't have to specify it). As each person clicks approve (it then dissapears, so they cannot click it again) the transition will not move to the next step, until the required number of approvals.