In Bigtop, we are using "Patch Available" state for that and it works pretty well, as far as I can tell. Here's the flow diagram for your attention:
https://issues.apache.org/jira/plugins/servlet/project-config/BIGTOP/workflows The case you propose below would be addressed by moving between "In Progress" and "Patch Available" until the fix is ready to be merged/committed to the mainline. If this is something that might work - and this is pretty standard flow, so no one will need to learn the ropes - you can ask INFRA to assign this flow to IGNITE project. Cos On Sun, Jan 18, 2015 at 10:23AM, Dmitriy Setrakyan wrote: > While we are trying to find a way to customize Jira workflow, in the mean > time we need to have a Jira status for issues that need to be peer-reviewed > by a committer. > > I propose using Resolve workflow for it. Whenever issue is ready for > review, Resolve it and assign to a committer who, in your opinion is the > best person to do a review. If the issue passes the review, then it can be > merged and closed. Otherwise, it should be reopened and assigned back to > the developer. > > Any objections? > > D.
