Global, loop transitions seem to have made it in to jira 6.4. See my latest comments on JRA-36498.

Update : Auo-Action are not altered on Workflow Scheme publication, nor Workflow Draft publication

Hi Josh,

Since JRA-33692 is always opened ... I continue with additional requests ...

Among OSWorkflows features, some of them (Join and Split) have not been used in JIRA for explicit technical reasons ... They are not easy to implement.

But one of them is functional and works correctly : the Auto Action.

I use it since JIRA 3.7, and ,in the same period of the 1st JIRA Workflow editor in Flex, I have also released another Workflows Designer in the Minyaa Suite. The goal was to provide a graphical editor and also to use some of feature of OSWorkflow (Global Transition, Recursive Transitions and Auto-Action).

Since JIRA Workflows Designer in HTML5, we have now a practicable Designer ... It has been hard to support the side effect of Workflow restructuration performed for the Global & Resursive Transitions, but it is now usable or almost !

Auto-Action are not yet available and we have to do with many constraints :

• XML edition to implement them, when Minyaa Workflow Designer is not installed (not yet validated againts 6.4)
• Force the reindexation due to the bug introduced for JIRA Agile (JRA-33293, JRA-31775)
  But, since WD 6.4, workflows designed with Auto-Action
• and probably (I am about to revalidate it) have to use the Copy To feature.

Since last week, I have started the migration from JIRA 4.2.2 to 6.4.2 for client, where we have use intensively the Auto-Action, and it appears that WD 6.4 is not able to display Workflow with Auto-Action (see screenshots) :

• Workflow with Minyaa
  
• Workflow with JIRA Workflow Designer
  
• Workflow with JIRA Workflow Editor
  

Is there some visibility in the road map of the Workflow designer for :

• supporting the display of Auto-action
• allowing to implement them
• allowing developper to extend the Workflow Designer

Thanks
Vincent

Hey v_thoule, I'll take a look today and see if I get it sorted out.

I know ... The plugin is added in Marketplace but I can not publish it. I think that Atlassian should perform a validation for any 1st release of a plugin.
Exact mhenderson ?

You can find it attached to this email jira-plugin-alkaes-workflows-tools-1.0.0-SNAPSHOT.jar.

Vincent

Vincent:
https://marketplace.atlassian.com/manage/plugins/com.alkaes.jira.jira-plugin-alkaes-workflows-tools

Page not found

My IT team did the upgrade and the version was pulled from the Atlassian website.

As for Zac's comment, I determine whether the transition is global or not, by inspecting the ID# in parenthesis by the transition name when viewing it in text mode. In 5.2.11, I would see the same ID# for each global loop transition assigned to each status. There were six unique ID# and I was able to select and update one of these transitions and the change would be reflected across all 6 statuses. Once I upgraded to pre6.3.11, I had 36 unique ID# and if I want to make a change to one transition, I had to manually propagate it to each of the statuses' transitions representing that previous global loop transition.

I'm definitely interested in Vincent's plugin and I'll give it a try today.

Hi All,

I have just pusblished in Marketplace (Not yet validated, then attached to this Suggestion ticket) a new plugin (com.alkaes.jira.jira-plugin-alkaes-workflows-tools) that may help you to have a workaround with this issue with Global Transition.
I did not have yet time to write a detailed documentation, but its usage will be easy to understand.

With JIRA 6.3, you are able to use WFD 6.4.x, then you can design your Workflows with Global Transitions.

There 2 case :

• You are editing a Draft of an Active Workflow
• You associate an Inactive Workflow in a Draft Workflow Scheme

In both cases, as soon as the design of your Workflow (WF1) is completed, make a copy (Copy Of WF1):

• Copy when saving the Draft
• Copy before associating it in the Worklows Scheme

When WF1 is active, the Global Transitions are converted in n Step Transitions.

The provided plugin allows you to make a "Copy To" of an Inactive Workflow directly to an Active Workflow.
The XML Descriptor is directly copied. In this 1st version, there is no check to verify that the Source and Target Workflows have the same Step / Status Id.
It should be done in a future version (as soon as I have time). An automatic Backup of the Target Workflow will have also to be done.

Attention, it is under your responsibility to verify which Worflow is copied to.

Regards
Vincent

And I really appreciate the willingness to roll this back. I've been frustrated with past Atlassian decisions that were declared as "we're never going back, deal with it" or "we're never going to prioritize this request, deal with it". So while the change was frustrating, your response is extremely refreshing. Keep it up!

Hey zach@42lines.net, thanks for the feedback. You are right, we should do a lot more of this UX outreach stuff, and particularly to advanced users as this is where we find that can get the decisions wrong. As I am sure you can imagine, our data sometimes tells us that something will be fine for maybe 80% of people, but it doesn't come with context and hence the last 20% of people are affected by the decision much much more. My teams understand this reality much better now and I can only say that we will continue to do our best to get the advanced user base involved more as we work on things.