Start Progress causing issue because of Post Function since 16-Aug-2015 update

[Mark Borg]

Start Progress is causing the following error:

I noticed that this happens because of a Post Function to Start Progress on parent ticket also. This only happens when parent is already In Progress.

I'm opening this ticket because the workflow has been like this for a while but the issue only started this week after the scheduled maintenance on Sunday 16 August 2015

C85BBCF26A9433EDCF3BF272FF5FC7F0FED1C579CD1D50923Fpimgpsh_fullsize_distr.jpg

[Mauro Badii]

JIRA Misc Workflow Extensions plugin is having issues on JIRA Workflows due to incompatibility with the last upgrade on Cloud.

You can find more info at https://jira.atlassian.com/browse/JRA-44681

[Pilar]

I would suggest you to delete the workflow postfunction and confirm if this error is definitely caused due to the post function.

If it does, then you can go through the workflow postfunction documentation again and set it up properly. Also maybe a good idea to test it on a test instance first.

https://confluence.atlassian.com/display/Cloud/Advanced+Workflow+Configuration

Pilar

[jcimaszewski]

I am experiencing this, as well. As Mauro explained, the issue is occurring with JIRA Misc Workflow Extensions interacting with recent updates. That exact problem is that when using the post function to transition a parent status, an error is being thrown now if there is a condition on the parent transition that is not being met. In my scenario, it is because I have a sub-task blocking condition configured to prevent transitioning while there are unresolved sub-tasks.

This worked before with no errors, but now there is nothing that I have been able to do to fix it other than remove the condition or remove the transition from the post-function. Both scenarios leave me with undesired an effect.

[Michael Durkin]

Just to echo what  Mark Andrew Borg is experiencing......

I am using the current JIRA OnDemand and had already, and successfully, been using the transition parent as follows: Using a parent "Global Transition" and a parent conditional that requires all sub-tasks to be either "Complete" or "Done" , when true, it transitions the parent to its "Done" state.

Now, I too am receiving the error message described above.

The mentioned workaround, "Make the Transition the parent has to go through a Global transition." was already in place.  

When I originally created the transition for the parent it was "Global" and each subtask workflow, respectively, post function (last line) is set to to "transition # will be triggered on the issues' parent issue.

So, it was working fine and now is not.  That is troubling and frustrating at the same time.

Sure, I could removed the post function to transition the parent, but that does not resolve what use to work.

Any comments appreciated.

[Mark Borg]

I deleted the post-function and I now can Start Progress on the sub-task.  

The thing is that this workflow has been in place for a couple of years now and hasn't been changed recently.   This was working fine before the scheduled maintenance that happened on Sunday the 16th of August 2015. The system would not give this error if the parent was already In Progress before this week.

Also https://confluence.atlassian.com/display/JIRACLOUD/Advanced+workflow+configuration does not mention anything about transitioning parent ticket.

[Dave Meyer]

Hi @Mark Andrew Borg, This is because we released an update to JIRA on 16 August that changed JIRA's behavior. As I mentioned here (https://jira.atlassian.com/browse/JRA-44681) we believe JIRA is now behaving correctly, and the previous behavior where the subtask would transition even if the parent issue transition failed was incorrect. So that's why this error just started appearing this week. I sincerely apologize for the disruption.