Tarun Sapra Community Champion

it's crucible not confluence, do you mean to use confluence integration with analytics as a dummy?

Hi Burton, I have done it in my workflow - Do the following - On all approve transitions add a condition- if all sub-tasks are approved and in the post function add the transition ID where in parent can move to approve. Suppose if you have 2 sub-tasks - So now if sub-task number one is approved it fires the post-function…

Hi @Jamie Echlin [Adaptavist] , I was going through the source code, I think I only saw the ones which are using it, thus I was confused, I wanted to see some example source code in order to write some JQL functions of my own.

I am using JIRA 5.2.11

or can you try to explicitly try mentioning "Epic LInk" in the additional condition section like in example - checkLink = {link -> <a href="http://link.issueLinkType.name" rel="nofollow noopener noreferrer">link.issueLinkType.name</a> != "Cloners"} , so instead of cloners you can mention "Epic Link" 

What's the JIRA and ScriptRunner Version that you are using?

it's working here - https://answers.atlassian.com/questions/12258914 

nice to hear, could you please accept or upvote my answer. thanks.

"This will exit the Creation process and leave an inconsistency on issues. Make sure the "Creates the issue originally." Post Function is first in the Create transition."

please see here - https://confluence.atlassian.com/jirakb/issue-screen-displays-error-rendering-greenhopper-epics-issue-web-panel-779158857.html

"I'm getting this error when looking at the Epic after I do this" - Do you mean Task or Epic?

the same thing here - https://answers.atlassian.com/questions/13418341 (answer by user Dima Pasko ) Also, make sure that you have "Epic Link" issue added on the "Screens" of the issueTypes which are being cloned.

Please see here - https://answers.atlassian.com/questions/211505 issue.setCustomField might not be right

Hi Matt, In the workflow for that issueType you can add a screen on the workflow transition for resolution such that the screen contains "Link" field, thus when the issue is transition to a certain state then the user can set both Resolution and Link it to another issue as well

Hello Sindhu, please accept my answer if it fixed you problem. thanks.

Make sure that the Columns of the Scrum board are mapped to statuses which include the status of the missing epics, as issues only appear on the board if their workflow status is part of the board configuration's columns.

Well there are lot of things currently in JIRA which I find very user-unfriendly , trying migrating "issueType" scheme of a large and complex project having lot of custom fields and you would feel like jumping out the window ! :D

Hi Rutger,I can understand your pain as it took me one whole day to fix this issue when I first encountered it, in one of the jira instances that I was managing. Also, please accept/upvote the answer if you feel it helped.

It's not a bug, or may be you can call it a bug because things aren't very clear. There can be couple of scenarios why it's happening - 1) Are you using classic boards? Some of the classic boards in plan mode must be having issues grouped under the fix version which you are trying to delete thus resulting in "re-appearing"…

where to change the css?

Priorities can not be set at component level. But there is an small hack which I use to prioritize based on components. What you can do is to create "swim-lanes" in your scrum/kanban boards, these swim-lanes will be based on components and then you can arrange the swim-lanes based on your component's priority, example- The…

would be nice , if you upvote my anwers :)

I think your missing something very minor, here's how i did it - My global transition - Hide transition from the user (the transition can be triggered only programmatically or from a workflow function). — AND All sub-tasks must have one of the following statuses to allow parent issue transitions: Closed. Now from subtasks,…

Please post your WF condition.

Value field for Status as compared as String, so if you put name in the condition instead of Id, that might work.

Hi Jayashree, You can add the condition in the global transtion in which you can specify the value field as the status with the value as the originating step. https://jsutil.atlassian.net/wiki/display/JSUTIL/JIRA+Suite+Utilities+Workflow+Conditions

Hi Jayashree, Add a global transition in parent workflow from eact state to final state and make it hidden in the parent workflow. and subtask should trigger this transition in their post function.

Answer from oilspace is partially correct - but to complete it is to make the global transition hidden, thus use the hidden feature from workflow misc. plugin as well... and it works smoothly :) Complete WF condition - Hide transition from the user (the transition can be triggered only programmatically or from a workflow…

I am usin' 4.4.4 and hide transtion is part of workflow misc. plugin, it's a must have plugin for complex workflows. https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions

Below is the workflowcondition with AND condition for the global transition.Hide transition from the user (the transition can be triggered only programmatically or from a workflow function). — AND All sub-tasks must have one of the following statuses to allow parent issue transitions: Closed.