JPD Automation fails for no apparent reason

[Benedict Lubik]

Hey all,

maybe someone can help me figure out why my automation keeps breaking. Background: Me and my team added a custom field to JPD called "Roadmap" were we created the classic "now next someday" roadmap stages. Every Idea either has no or has one roadmap stage active, depending on the lifecycle or readiness.

I now wanted to add an automation to JPD were depending on the stage of the idea in our internal workflow (so basically the kanban column in JPD) JPD would then set the custom field "Roadmap" accordingly depending on a mapping that I specified. 

Now my automations aren't working because there seem to be multiple fields with the same name "roadmap". But there isn't in JPD, I can only select the one that I custom created.

Help. :D

[Adam Wencel · Accepted solution]

I'm following this atm since automation is a large part of what I'm testing atm.

Have you tried just adding something like "S" or "s" ("s" delineating stage) on the end of the roadmap custom field to see if it's system tied or not for the "roadmap" name?  Since there are no extensive white notes or administrative documentation of the full breakdown of JPD, I'm relying on others (like yourself) discovering these nuances.

[Benedict Lubik]

Yea that fixed it for me. Seems like JPD is missing some depth that I am used to from Jira

[Bill Sheboy]

Hi @Benedict Lubik 

For a question like this, please post an image of your complete automation rule, 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.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

Smart values are name, spacing, and case-sensitive.  And, as JPD appears to be based on team-managed projects, their fields are local to the project.  Those things will not prevent collisions of smart values (and field names) in rules.

To confirm you have the correct smart value for you field, please use the how-to article linked below.  And if there is still a collision by smart value (which would be unlikely after verifying it) you could use the custom field id instead.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

[Benedict Lubik]

Thank you Bill, I'll check it out :)

[Ted]

Maybe someone from the JPD team can better answer, but there is an out-of-the-box "Roadmap" field in each JPD project that you can use to tag ideas with. I just created a new test project to check this (see below)

I also checked that it is possible to select this Roadmap field in the automation module (see below)

If you have created a custom field called Roadmap, then when creating the automation as the fields are named exactly the same, Jira won't know which field to pull from and so the automation fails.

Maybe double-check whether you can find the default Roadmap field in your JPD project? You could then map your custom field Roadmap status' to it and then delete the custom one, and have another go at creating the automation. 

[Benedict Lubik]

Yeah I keep thinking the same... Is there some way to distinguish custom fields from "out of the box" fields? I can't tell if someone ended up deleting that one or if we are using that one.

[Ted]

@Benedict Lubik - when you go to the fields dropdown, how many Roadmap fields do you see? 

Alternatively, you could create a new JPD project, where you will have the Roadmap field and migrate your ideas there.