nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to do automation to compare child and parent custom field being string?

lukasz.lichota

I'm not sure where to start for this automation attempt:

I have custom field (single select, string) indicating a delivery cycle for the work item (e.g. 2021-Q4-1). This field is set both at Story and Epic level and I'd like to write a rule that checks consistency, that is that the Story level value is no later than what is in Epic. The format of those strings is such that alphanumerical comparision (grater, equal, smaller) would be the right one for me. Is this possible to write such a rule?

Accepted answers

Alex Koxaras -Relational-

Hi @lukasz.lichota

Interesting question you've got there!

I would approach your problem with a slightly different angle, and instead of comparing the values on the right I would compare the option ids of your single select field. That is if you have the ability to set it up like below:

id	value
1	2021-Q1
2	2021-Q2
3	2021-Q3
4	2021-Q4
5	2022-Q1
6,7,8,9......	etc

What I would do is to actual compare the id of the selected value, instead parsing the text inside your value. So e.g. if I had set up a rule either in automation or within a workflow (with the use of an app) I would check the relation between the two selected values of the field in both story and epic. If the id of the value in story is greater than that of the Epic then:

either don't let the user create the story (validator inside a workflow)
or change the value of the story to at least match the value of the epic (jira automation, and upon issue creation)

Would something like the above work for you?

All comments

Alex Koxaras -Relational-

Hi @lukasz.lichota

Interesting question you've got there!

id	value
1	2021-Q1
2	2021-Q2
3	2021-Q3
4	2021-Q4
5	2022-Q1
6,7,8,9......	etc

either don't let the user create the story (validator inside a workflow)
or change the value of the story to at least match the value of the epic (jira automation, and upon issue creation)

Would something like the above work for you?

lukasz.lichota

@Alex Koxaras -Relational- In terms of ids (I assume "id" is what is called "position" in the custom field value definitions) then yes, I can control that and it's already in right order, so if the ids are somehow accessible then comparing them is an option.

I don't know much about automation (only created couple of simple rules) so could you please advice how would I approach this task?

What I want is a scheduled job (schedule trigger) that will send an email or slack message with those issues that doesn't match. I thought I could use scheduled trigger with JQL query selecting a Stories I'm interested in. But then I'm not sure how to reach to parent and do the comparison.

Alex Koxaras -Relational-

You could either use REST API to retrieve this single select ID, or use a 3rd party app, like JMWE or scriptrunner to do the comparison on the create screen of your story workflow, or use smart values within a Jira Automation. The latter could be easier.

For example you could do the following with Jira automation:

And then on the audit log you would have these results:

Thus having two integers value to compare!

Happy ending, no?

lukasz.lichota

@Alex Koxaras -Relational- thanks a lot! I'm in the middle of testing it and I noticed that the ids are not the positions (in the custom field administration) but they are very high numbers (e.g. 12131) which looks more like global counter? Fortunately they seem to be in the right order, likely becuase of the creation time/order (if they are global order indeed) but once created they cannot be influenced I guess, is that correct understanding?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud