Please ask Dan Allen if we can reuse his Seam workflow and Seam workflow scheme.
Maybe we should rename it to something like "GIT pull request workflow" to be reusable.

By all means, reuse the workflow I put together if you can. That was my intention when I created it. I limited it to the Seam project while it incubated It's worked great for us so far, and I think it's time for it to mature.

There is one small problem in "Seam Workflow" workflow - "Pull Request Closed" step leaves "Resolution" on bad value "Unresolved".
Compared to standard "Resolve Issue" step it has no screen assigned. So solution is to assign standard "Resolve Issue Screen" screen to this step. I tested it on STAGING and seems OK. What do you mean Dan, may I add this to PROD too?

Second thing we need to solve if we want reuse this workflow is to map "Git Pull Request" field to other projects, because now seems to be mapped only in "Seam Field Configuration". So we need to enable it in "Default Field Configuration" too.

And we also need to modify configuration for "Git Pull Request" custom field to allow it for new projects.

I also noticed that "Seam Workflow Scheme" assigns "Seam Workflow" to only small subset of issue types (Feature Request, Bug, Task a Component Upgrade). I think more issue types is suitable for this workflow (Enhancement, Patch, Library Upgrade, Sub-task, ...).

And there is also problem to rename active workflows.
So I go to create copy from Seam workflow and Seam workflow scheme with all enhancements described here and use it for requested ARQ projects.
Dan can migrate Seam projects to this updated workflows if want (I tested this king of switch on our jira STAGING without problems).

So solution is to assign standard "Resolve Issue Screen" screen to this step. I tested it on STAGING and seems OK. What do you mean Dan, may I add this to PROD too?

Go for it.

So we need to enable it in "Default Field Configuration" too. And we also need to modify configuration for "Git Pull Request" custom field to allow it for new projects.

I had the permissions limited in scope for the purpose of prototyping. Now that we are moving forward with it, you can open it up to other projects.

I also noticed that "Seam Workflow Scheme" assigns "Seam Workflow" to only small subset of issue types

I excluded the other issue types because frankly, I don't know why we have them. They just confuse people. The less issue types there are, the better, IMHO.

Dan can migrate Seam projects to this updated workflows if want

That sounds like the best approach.

• new workflow "GIT Pull Request workflow" created based on "Seam Workflow" with patched "Pull Request Closed" transition
• workflow scheme "GIT Pull Request workflow scheme" created to use this workflow for issue types where meaningful
• "Git Pull Request" custom field reconfigured to be available for all projects for issue types where meaningful
• new workflow scheme assigned to ARQAJO and ARQRUSH project