When I go to workflow configuration in a project and assign an issue type to an workflow, JIRA (latest version) mixes up the issue types. This means if I assign Task to workflow 1, JIRA assigns Sub-Task. If I assign Bug to Workflow 2, JIRA assigns story.
I'm afraid I'm not understanding the question.
Could you tell us what you have in the workflow scheme for the project?
And then explain what you mean by "assigning workflows" - what's going wrong and where?
I have 4 workflows in my workflow scheme:
I have a new subtasktype (named Bug-Task).
I am assigning that new subtask-type named Bug-Task to the Bug Workflow. Whenever I save the change not the bug-task was assigned to the Bug Workflow, but another issue type.
Ok, I got most of that, but to be clear on the last bit - you go to the workflow scheme, click "add workflow" at the top right, select "bug-task" from both issue type and workflow? Then when you click "ok", you come back to
Is that right? What does the ????? say in your list?
@Nic Brough [Adaptavist] @Sven Weih
Did you ever find a resolution/fix to this bug? We are experiencing the same problem with v7.1.9.
I am trying to create a reopen transition from a terminating 'Closed' status. Since I am unable to edit terminating status on active workflow, I must create a copy. When I try to add the edited workflow back to my workflow scheme, JIRA associates it with a different issue type.
Please let me know if any fix was discovered.
Core 7.3.3 most definitely has a bug in here. Being in teh projects workflow scheme and attempting to assign issue types to another or new workflow, religiously fails. I have experienced this many times now, so it's a programming issue that it is ignooring the issue type selections being made. seems to be opting for wahtever issuetype it finds in its lists first.
reattempting this inside system admin as a stand alone WFS change is marginally better. here's hoping they fix this soon as it could be pretty data damaging
I have the same problem when adding new worflow to a scheme from the project administration view or trying to assign an issue type to a workflow. It seems to always assign the last issue type on list instead of the one i chose. It works correctly on workflow scheme edit in Administration->Issues->Workflow Schemes menu. We're using Jira Software 7.4.2.
The problem here is that no-one is replicating it. It doesn't happen on a 7.4.5 environment I've got access to (or 7.4.2, or 7.3.3 or any other), so the question is "what are you doing differently to the majority of us". It could be your browser, addons, customisations...
The error occurs in a set of conditions.
Result: The actual Issue Type assigned is not the one previously selected!
We have found this KB describing the same mentioned problem associated to the Zephyr Add-on. We have also reproduced the same behaviour with Calendar for JIRA Add-on.
First of all, mind that the procedure recommended could make some functionalities of your application unavailable, so we recommend you schedule a downtime validation window that would not impact the operation.
Do you know what the problems with the plugins are?
I have a plugin build by my own which is responsible for the misbehaviour.
But i didn't get any error in the logs and it works.
The only problem is the configuration of workflow schemes.
How can i fix it if i didn't know what the problem is :(
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs