nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Changing an issuetype via transition, JIRA gets confused after another transition.

Ronny Tsee

Hi there,

I have a service desk and created a custom workflow.

I have added a post function where a transition changes the issue type.

Once the issue type is changed, the workflow also changes.

However when I resolve the issue, it gives me transitions that are not linked to the status,

Can you help diagnose this?

Accepted answers

All comments

Alexey Matveev

Hello,

For what plugin is the post function, which changes the issue type?

Raynard Rhodes

It seems your transitions are not matching the workflow.

It's interesting, can you show all transitions in your screenshot?

Ronny Tsee

The add-on am using is JIRA Misc Workflow Extensions

David Fischer

Changing the issue type field should only be done if the workflow doesn't change. And even then, it's a dangerous proposition because there might be required fields on the new issue type that are not required in the old.

JMWE doesn't currently offer a "move issue" post-function, which is really what you would want.

But in general, moving an issue is not necessarily a good idea for traceability reasons. You might want to clone the issue instead.

Yogesh Mude_u145qk

HI @Ronny Tsee

Please check which workflow is associated with the Service Request Issue type.

Ronny Tsee

Thanks David I will propose this to the team

Ronny Tsee

The associated workflow is correct.

Raynard Rhodes

You mentioned the Issue Type changes. What does the Issue Type workflow look like for the second one?

Ronny Tsee

The second workflow is the one attached in the previous replies.

The initial workflow is:

The options after the change works fine, the transitions from there are correct, the wrong transitions appear only after I resolve the issue.

Raina Anand

Does a 'move' issue exist now?

Nic Brough -Adaptavist-

No, because the change of issue type is structural, it would damage or destroy the issue if done during a workflow action.

"Move" is something that should only ever be done by hand (albeit bulk-move is fine), because it usually affects the structure of the issue. The only time you could do it automatically and safely is if the target project/issue-type has identical configuration to the current one. Same workflow, same custom fields and field configurations. (Different screens won't break it but may lead to odd behaviours).

Imagine the case in which you will destroy the issue - if you move an issue to a project/issue-type combination that is using a different workflow. As soon as you have completed the move step, you now have an issue that cannot complete the rest of the transition because you've changed the workflow.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

server

jira

jira-server