Create delivery tickets by automation

Rebecca Graf

Hey all,

 

I'd like to create a delivery automatically once a JPD ticket reached a certain status and has dedicated field values.

I already tried to achieve that with a global rule, but the link was not set:

When issue transitioned from to

And: bucket equals initiative

And: No linked issues match Types: is implemented by, implements Match project = INIT (to ensure that there wasn't already a delivery ticket created)

Then: Create a new Initiative in Initiatives

And: Link issue to trigger issue 

 

The error message I got is:

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - 

Linked Issues (issuelinks)

Both projects (Jira and JPD) us the implements / is implemented by already to link delivery tickets, but so farthis is only set manually. 

Any ideas what needs to be changed to make that rule work?

Your help is highly appreciated :-)

Best

Rebecca

 

Nick Haller

Hi @Rebecca Graf ,

I think an automation like the one below should work for your use case:

 

1) WHEN: Issue Transitioned to (select your workflow's / idea's status)

2) AND IF: Issue fields condition (select your Bucket field = Initiative)

3) AND IF: Related issues condition

• Related issues = Linked issues
• Link types = implements, is Implemented by
• Condition = Are not present

4) THEN: Create issue (select your Jira project / issue type)

(If you were to copy any of the JPD idea's fields to this Jira issue's fields, copy from Current issue)

5) AND THEN: Link issues

• 6) Link issues: is Implemented by - Most recently created issue

 

I tested with the automation above after those fields / conditions were met, and it worked as expected.

 

But the error you shared sounds similar to what other customers have run into where the A4J (Automation for Jira) user has not been granted JPD permission. 

To have this corrected, you'll want to open a ticket with JPD support so they can grant your A4J user with JPD permission. The A4J user cannot be granted permission from your end.

You can open a ticket within JPD support HERE, or under the Give Feedback tab >> Get help from the support team. 

 

A workaround for the time being is adjusting the Actor of the automation to a user that has JPD permission to see if results vary and/or are successful.