Creating an automation rule between Jira Discovery Project and Jira Software Project

[Selena Peri]

Kia Ora... my query is related to Jira Discovery Project... I'm wanting to create automation between Jira Discovery Project and Jira Software Project for the following scenario:

When my 'xxx Jira Discovery Project' issue/ type: Idea changes it's status to: xxx
Then in my 'xxx Jira Software Project' I want to clone the 'xxx Jira Discovery Project' issue/ type into my 'xxx Jira Software Project' as an Epic record and status set to: xxx

I've created various automation rule configurations in Global Automation and when I run the rule there i no cloned issue.
Rule at follow:
When: Issue Transitioned... to 'xxx'
If: issue matches JQL (query filter for which type/ issues that need to be considered when a status change is made)
Then: Clone issue into...

Have tried many different selections in the rules but can't get the dynamic automation working.

I know I can clone the Jira Software Project via "create delivery ticket" - but I'm wanting to setup automation as there are other fields that I want to automate once I get the status change triggering a clone issue.

[Dexter de Vera · Accepted solution]

Hi @Selena Peri ,

Welcome to the atlassian community,

You can create sample automation like this:

Create, link issue, copy field and move status of new issue in xxx software project when xxx Jira Discovery Project ticket transition to xxx

When: Issue transitioned - To status xxx

Then: Create issue:

        project: Software Project XXX

        Issue type = Epic

        summary = {{issue.summary}}

       choose field to set = select all fields you need to set/copy including linked issues

        Linked Issues = implements - Trigger Issue (so this will be shown in Discovery tickets)

       added issue field = set or copied from Trigger Issue (from xxx Jira Discovery ticket)

Add a Branch: Branch rule / related issues - Type of related issues = Most recently created Issue

Transition issue: Destination Status = xxx

[Selena Peri]

Kia Ora @Dexter de Vera 

Thank you and appreciate you reply to my post asking for automation support between two JPD and JSP.

I configured my rule as you explained but I still received an error.

I'm unable to add my screenshots to show my configuration setting and the error received...

However, "some errors" states:
Create issue
unknown field set during create, they may be unavailable for the Project/ type. Check custom field configuration. Fields ignored - Linked Issues (Issuelinks), Description (description)
Error creating issue
Bad Request (400)

So - I unchecked Linked Issue and Description fields, in the "create Issue" pop up window... "some errors" now states:
Create issue
Error creating issue
Bad Request (400)

hmm...

[Dexter de Vera]

Can you show us screenshot of your rule?. Did you check the linked issue and description are in your software project epic create screen. And also check if there are other fields that is mandatory upon creation of epic.

[Selena Peri]

Kia Ora @Dexter de Vera ,

Again, thanks for your reply... have attached screenshots of my settings selected for this new automation rule.


Good call out point about the 'new Epic creation' - what other mandatory fields must be filled in when raising a new Epic issue -> will check that.

And, I seem to get error log for "linked issue"...

Again thank you @Dexter de Vera  - for helping me here...

[Dexter de Vera]

hhmm. your automation is correct. Do you indicate the Software Project in Create issue? and in Audit log the trigger issue is from product discovery Project right?

Can you try again to create manually in Product discovery project  via "create delivery ticket" (use both project you indicate in automation).  and if its successful without any additional field needs to fill up. Then try again the automation you created. this maybe a bug in automation that you need to raise in Atlassian Support .

[Selena Peri]

@Dexter de Vera ....

Yes, I do in 'Create Issue' indicate the 'Software Project" that the new Epic needs to be raised in...
However,  with this question: and in Audit log the trigger issue is from product discovery Project right? - are you asking that the Discovery Project is showing up as the 'trigger' issue?
Yes in the Audit Log it states "associated item: issue event" lists the Discovery Project issue that I had just transitioned status'.

I am successful in creating a new issue via "crate delivery ticket"...

Also, in my Software Project Epic screen... default field: Description has been removed... I have three custom fields and Summary field as defaults.

[Dexter de Vera]

You mean there is no field for description in software epic? Make sure all the fields needed in create issue action (automation) is included on all screen of your epic screen scheme.

[Selena Peri]

Kia Ora @Dexter de Vera 

Thanks for additional reply.

Yes, my Jira Software Project (JSP) Epic Creation doesn't have "Description" field as a field that's either available to fill out on the 'issue'.

It seems via the Jira Discovery Project's (JDP) UI it's OK to create a Epic issue... and it pulls the "Summary" field context all ok... 
However, via the 'automation' (back-end) 'create new Epic' isn't created.
It seems, in the JSP, where I want a new Epic created, nothing is triggering - as the Audit Logs show no errors but the Audit Logs in the JDP does show the error (Bad Request (400).

Will also raise a support ticket... while I keep working on the following rule:

When: JDP issue transitioned to: xxx (from any status)
Then: Crate a EPIC (in JSP)
          Copying the "trigger issues' Summary (trigger issue type = Idea, in JDP)
          And, transition 'target issue' (new Epic created in JSP) to: xxx

hmmm...

[Dexter de Vera]

The automation I shared with you is working on my side. (Screenshot is tested successfuly) before I show it to you. Lets wait for Atlassian Support feedback.

[Selena Peri]

Kia Ora @Dexter de Vera

I have managed to get the automation working now!

The rule setup you explained worked perfectly - thank...

It was just my end needing to configure where to pull the data from in the 'trigger issue' -> e.g. {{xxx}}... the info 'xxx' needed to be the field in the trigger issue that I wanted to have copied over into my JSP Epic issue field.

Thank you again!

[Dexter de Vera]

Great! Happy to help.

[Hermance NDounga]

Hi Selena, 

Can you please open a support ticket, specifying which project and which rule you're not able to make work? 

to open a support ticket, go in Jira Product Discovery, and click "give feedback" at the bottom of the left navigation, and then choose the support team

Thanks! 

Hermance