Jira Product Discovery Automation - Move Items from a Jira Project to Jira Product Discovery Roadmap

[Jack Young]

Hello,

Recently signed up to Jira Product Discovery having learned of the new very useful features it has to offer. The Roadmap in Jira Product Discovery is exactly what i have been looking for in Jira for sometime now and now its available i can ditch the other products i was using to display our project roadmap to our Stakeholders / Sponsors.

I find it extremely useful how you can publish views and share information with people that do not have a licence to the Jira Software. 

I would like to use this tool as a way to display our progress those that need it.

My Question:

Is there a way using the Jira Automation tools available to when a task in a standard Jira board hits a certain status can be either Moved, Cloned or Created in a Jira Product Discovery Roadmap? 

When I have tried this, there seems only be the option to Clone or Create an issue using the inbuilt automation, Moving a ticket seems to not be an option yet. and when i have tryed to use the clone / create automation steps there seems to be some errors thrown back when creating / cloning the ticket from its current ticket type to the new "Idea" type. 

Example of the error when cloning:

Example of the error when trying to use the Create Issue:

When I "move" the ticket manually from a standard Jira board to the Jira Product Discovery it works fine, there are a few screens asking for the specific Idea issue type field to be populated but these seem to not be required so shouldnt be an issue aslong as the ability to move a ticket to a new project using automation is available (which it currently is not). 

Does anyone have any ideas / solutions to move a ticket from a standard Jira project into a Jira Product Discovery Roadmap Project using automation as the Jira Product Discovery Tools seem to have Huge potential when reporting to the wider business?

[Bill Sheboy · Accepted solution]

Hi @Jack Young -- Welcome to the Atlassian Community!

While it is theoretically possible to move an issue from one project to another with an automation rule (using the REST API endpoint), it could have many challenges due to differences in permissions, issue types, workflow, fields, etc.  This is one reason the UX has a specific "Move issue" feature to guide the steps, asking questions when needed.  Automation rules cannot pause to ask questions, thus all possible challenges need to be predicted and handled in the rule.

Instead, using the Clone Issue action (perhaps followed by closing the original issue with a relevant Resolution) is better.

When doing this to clone to a JPD Idea, ensure the rule has the correct permissions (and potentially rule scope) to access what is needed:

• Please check the rule actor to learn if they can create Ideas and set your fields
• When attempting to do anything more than clone / create an issue in a different project, the rule must have multiple-project or global scope.
• Some JPD fields are dynamically calculated, and cannot be set by issue edits, create, or cloning

If you are still having trouble with your rule, please note context is important for the community to help.  Please post the following:

• what type of software project is this (e.g., company-managed, team-managed, etc.), 
• an image of your complete automation rule in a single image for continuity,
• images of any relevant actions / conditions / branches,
• an image of the audit log details showing the rule execution, and
• explain what is not working as expected and why you believe that to be the case.

Kind regards,
Bill

[Jack Young]

Thanks for this @Bill Sheboy,

Your description was very helpful and i managed to acheive what i needed, my issue seemed to stem from the automation actor...

Seems i needed to change it to the account that has the creator permissions.

Thank you for your assistance.

[Luka Hummel - codefortynine]

Hi @Jack Young

If you’re looking for an efficient way to move items from a Jira project to Jira Product Discovery while maintaining structure and details, our app Deep Clone for Jira could be a valuable solution.

With Deep Clone, you can:

• Bulk clone multiple issues at once, making it easy to transfer relevant ideas or roadmap items.
• Clone and move issues between projects while preserving fields, comments, attachments, and more.
• Automate cloning using Jira Automation in combination with Deep Clone’s post-function capabilities.

For step-by-step guidance on setting up automation with Deep Clone, check out our documentation.