It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Moving Issues: How to make a shortcut list of destination projects and types?


We have a Support project that's used as a generic intake location for all sorts of issues. Very often, the reporter submits the wrong ticket type, and we need to Move the issue into the correct place. (75% of the time or more)


We have 20+ projects and 30+ issue types in our system. However there's only ~7 commonly used combinations for these situations. We would like to present the Support staff with a short list of options. Once selected, kick off the normal Move process (to handle complexities like changes to fields, workflows, etc.)


  1. User creates ticket as SUP: Support Request
  2. Support team opens ticket, determines that it needs to be moved. Options presented:
  • SUP: Account Request
  • SUP: Content Help
  • DEV: Feature Request
  • DEV: Bug Report

1 answer

0 votes

Hi Marc,

Thanks for the background on your goals with the workflow, and this lines up with something I have been working on in a test site recently trying to figure out a native option as a workaround to this.  It still needs some polishing but is a good starting point to get you going.

 A little background, historically this is something that has been blocked by a few different long running feature request, but an option opened up recently specifically for service desk projects where you could do this with the native Service desk automation rules, and you can now create an issue based on action in the service desk project, Noting the Service desk automation rules will get very complex very fast to do the necessary update operations notes on this below.  But while you are checking this out Let me know if you have any Questions on this as I know its a huge wall of text, and a lot of steps, and there is a lot of room for improvement based on individual use cases, but it’s a good basic approach.

First, as an initial reference point and background on the feature, details on configuring Automation rules can be seen here:

Beyond Automation rules there are third party apps to extend the functionality further, and have options to do this as well with scripted actions to accomplish this, and my have more simplified methods for this particular task and I would recommend looking at a fe of the apps to see if they would work for your process.

For the add-on apps you could use something like Automation for Jira, or Add Issue on Transition for Jira Cloud, or ScriptRunner for Jira, as an exe of some apps that would give you additional options for this, but check out the Marketplace apps I linked and  the related apps section as there are a lot of options if you go this route, and you can check the documentation for each to see if it fits your needs better than the native options.

Back to the native functionality a big point I want to stress is that the logic can get pretty complex on simple actions when trying to trigger automation in two projects that are reliant on cross project actions because of the order in which the action is completed to when the issue is created/updated and then indexed.  Because of this there is a lot of potential for logic conflicts with automated tasks as you will need them to fire in very specific orders so that action one in project 1 triggers the follow up action in project 2 which in turn triggers another follow up action in project 1 etc.... . As an exe if you have two two automation rules on the issues creation where one created an issue in project 2 and the other transitions the issue in project 1, and tried to have an "on linked issues transition" in project 2 that triggered a follow up action there would be a conflict as the transition portion could not be seen by issue 2 as it is in the process of being created when issue one is transitioning and the automation action will be missed.

So the following example is an ultra simplified version of how to set this up, but still gets complex fast so I recommend setting up some test projects to play around with, per your specific requirements before applying any changes to the production projects.

So my simplified outline of the approach using the native automation functionality would be as follows:

Project setup:

  1. I am using only two projects in my example 
    • a Collection Project
      • DeskTato” DESTATO
    • a Destination project 
      • “Potato Desk” PD 
    • but this can easily be extended to multiple destination projects if desired with additional logic In the automation 

The Collection Project “DeskTato” creates and maps issues in the Destination Project “Potato Desk” using a unique identifier in the form of a type “Select list (single choice)” custom field value to create the desired issuetype/request type in the destination project.  

At this point, you can get as complex as you would like, adding in several fields to work out the necessary logic for the 20+ projects and 30+ issue types you noted, I am sure there will be some necessary trial and error to work out the logic, like which destination project, differences in issue types in the projects, needed field types for required fields on the various projects, etc... noting the more fields or projects given as an option the more complex the automation rules will become, and I am looking to expand Multilevel cascading fields into this process for version 2 as described here “Jira Service Desk: How do I create a conditional field?“ but I’m still working out some of the logic there, but I think this is worth investigating on your end as well because it would be really useful for the 20/30 issuetype/projects that your trying to combine to help narrow the scope of the input options.

Again In my example automation rules I am using one field for the choice to route to one new project and splitting the issue in the Unique identifier into alternate request types on the destination project:

  1. Set up one collection project that will be used as the data collection point
    1. Set it up with a simple workflow with the statuses of "Open" and "Done" only. 
    2. Set a post function on the mark as done transition to set a resolution
    3. and do not set screen for the mark as done transition
    4. On the Done status add an issue property of jira.issue.editable = false 
      1. This prevents a duplicate comment form one of the automation rules later on

  2. In the Destination projects Edit the workflow to have a looping transition from the first status back to itself through a secondary Status exe: Create > Open > Automate > Open > rest of the workflow Like this
    Screen Shot 2019-09-16 at 9.48.14 AM.png
  3. In the Data Collection project Create a "Select List Single Choice" custom field that will be used to route the issue to the appropriate project. 
    1. Add one option for each project or request type that you want to create the new issue in. 
    2. In the EXE I have options S1, S2, and S3
  4. Add the custom field you created to the request type's customer visible fields and set it to required = YES
  5. In the collection project Create 3 Custom Rules In the Following Screenshot I used the naming convention of P#A# pr project and Automation rule number to explaing the mappings so P1A1 is project 1 Automation Rule 1:
    Screen Shot 2019-09-13 at 3.23.26 PM.png
    1. P1A1 the First custom automation rule P1A1 Triggers P2A1, When the Issue in project 1 is Created, it will Create New issue in the Secondary Project based on custom Field value using the automation rule:
      1. When This Happens...
        1. Issue created
      2. Then do this...
        1. Create Issue
          1. Then using the onscreen dialogue to configure the desired field values and insert variables such as setting the Issue type or wether to copy over the summary and description, and what project this will be created in, Noting: a request type cannot be set at this step more on that below.
            Screen Shot 2019-09-13 at 3.27.20 PM.png
          2. Save the Do action option and
      3. Choose the Add Condition Option to enable the If statement selection set this to:
        1. If These Match....
          1. Select “Switch to JQL”
          2. Add the statement "Select List EXE" = S1
      4. Choose the Add Branch option to add a "Otherwise Do this.." section and Repeat steps 1-3 above for each JQL combination of field options you want to be routed to an alternate project, and save the automation rule and you’ll have something like this:
        Screen Shot 2019-09-13 at 3.31.56 PM.png
    2. P1A2 the Second Automation Rule Triggered by P2A1, Triggers P1A3, When linked issue triggers the Loop transition, add comment with link to Portal for location of new issue, with the settings
      1. When this happens...
        1. A Linked issue is transitioned
      2. If these match...
        1. Issue matches: status in (open)
      3. Then Do this...
        1. Add comment
          1. Write up a custom comment to add to the issue noting the base portal URL for the customers open requests something like
          2. "Based on the values you have input a request has been submitted to [This Portal | https://<BASE_URL>]"
            Screen Shot 2019-09-13 at 3.36.29 PM.png
    3. P1A3 the Third Automation Rule in project 1, Triggered by P1A2, Triggers P2A2, Auto Close the issue
      1. When this happens...
        1. Comment is added
      2. Then Do This...
        1. Transition Issue to "Mark as Done"
          Screen Shot 2019-09-13 at 3.44.49 PM.png
  6. On the Destination Project create Three Automation Rules:
    Screen Shot 2019-09-13 at 3.51.30 PM.png
    1. P2A1 Triggered by P1A1, Triggers P1A2, launches looping transition open to open
      1. When This Happens…
        1. Issue Created
      2. Then Do this…
        1. Transition issue to :”Automate”
          Screen Shot 2019-09-13 at 4.31.59 PM.png
    2. 2A2 Triggered by P1A3, sets request type so issue will be visible to end user, Per the note above on the issue create in P1A1 where the request type could not be set at that location:
      1. When This Happens...
        1. A linked issue is transitioned
      2. Then Do this...
        1. Edit Request type
          1. Select the desired request type (This is necessary to make the issue visible to the user that submitted the initial request)
      3. Add a condition to Add the "If these match.." section
        1. Linked Issue Matches,
        2. Switch to JQL, and you have two input options:
          1. If you have one project for each of the options just add in
            1. status = Done
            2. Repeat for each project with a custom rule per project
          2. If you have multiple request types in one destination project add in
            1. status = Done AND "Select List EXE" = <the Field option that is tied to desired Request type>
            2. Add Branch in the same rule
            3. Repeat this for each request type
              Screen Shot 2019-09-13 at 3.55.45 PM.png
    3. P2A3 Triggered By P1A2, Set the issue back to open from the Automate transition so you can start working on the issue like it was created there initially
      1. When This Happens…
        1. A Linked issue is transitioned
      2. If matches
        1. Status = Automate
      3. Then Do this…
        1. Transition issue to “Back to Open”
      4. This is where the jira.issue.editable = false step comes into play as an additional notification and comment would be triggered here if the workflow property is not in place:
        Screen Shot 2019-09-13 at 4.35.14 PM.png

Now if you Create an issue in the data collection portal, a new issue is created in the Working Project with the different request type per the Custom Field selection in the first portal.


Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you