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; } } }

Is there a way to move an issue using automation?

Danno

I am trying to update an existing project to limit the what issue type a user can create. I've tried other methods and thought it might be possible to use the built in Move function in an automation rule. I don't see a native way to do it but am hoping for a clever solution.

Smartvalue solutions are acceptable.

*Note: Please don't reply if you are going to suggest an app add on solution. Those are not an option here.

Accepted answers

Walter Buggenhout

Hi @Danno,

There is no out of the box action in automation to move one or more work items, but as per this feature request (JRACLOUD-70305) the REST API has an endpoint available since September last year that you can call from automation rules.

That might actually offer possibilities ...

Hope this helps!

All comments

Walter Buggenhout

Hi @Danno,

That might actually offer possibilities ...

Hope this helps!

Walter Buggenhout

Apart from that - if you don't want people to create work types in your project, is there any reason why you could not simply remove the unwanted types from your project?

Danno

@Walter Buggenhout my brain was fried from trying to make some changes to an existing project without tearing up too much of it. I actually tried using the create permission property from another answer you had posted to someone regarding this same type of want.

Can the workflow properties be limited to an issue type?

Create separate workflows for the two issue types and lock one out via properties. I had given up on it to the point of using automation to create the correct task and delete the one I didn't want them to create.

Of course, that gave me heartburn knowing I would have many issues with keys that were out of sequence. Create issue KEY-###1, spawns KEY-###2, and deletes KEY-###1. 🙄.

Finally some sort of wave of clarity came over me. The solution follows the KISS principal. Upon creation of the wrong issue type you just edit the issue. See below.

Change issuetype rule.png

It works like a charm since I am staying in the project.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

issue-type

move

jira-automation