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; } } }

Issue summary with conditional logic & smart values

David Quiram

I want an issue summary to contain custom field information but with a little logic.

Stick with me here...

The issue will have one of two potential date fields filled in depending on other options in the issue. So for ease we will call them issue.CustomDate1 and issue.CustomDate2

I want the issue Summary to have some text and then insert CustomDate1 -OR- CustomDate2, whichever field has a value as the other will be null.

How would that be scripted?

Accepted answers

Jack Brickey

if one is always empty try just including both...

Action - edit issue - Summary

{{issue.summary}} - {{issue.due date}} - {{issue.other date}}

this will append both dates but if say the first is "none" then you get this...

this is my summary - - 2202-02-23

as an example

All comments

Curt Holley

Hi @David Quiram

At a high level it would go like this:

by using the {{issue.Summary}} smart value, the automation repopulates the existing summary. Then by added {{issue.duedate}} (or in your case, one of your custom date fields) you get the date after the Summary.

You could simply do a rule for each field or use an If/else condition.

You can also format the date to best suit your needs. See Jira smart values - date and time | Cloud automation Cloud | Atlassian Support

Jack Brickey

if one is always empty try just including both...

Action - edit issue - Summary

{{issue.summary}} - {{issue.due date}} - {{issue.other date}}

this will append both dates but if say the first is "none" then you get this...

this is my summary - - 2202-02-23

as an example

David Quiram

So this Summary is being filled in on a linked issue during a Create Issue action in an automation flow. Hence why I was looking for conditional logic in smart values.

David Quiram

On a low level, this could work. We would just a random space that nobody will realize except me.

As someone who likes easy solutions, this appeases me 😎

As someone who is OCD and is unnecessarily focused on formatting, this annoys me 😑

Curt Holley

That can be done @David Quiram via branching and some smart values. Best you state your complete use case so we can provide more focused responses for you.

David Quiram

OK, hopefully this helps clarify everything for you.

Automation will check an issue on creation and create a linked issue in another project if it meets specifics requirements. That is all working just fine.

On the created linked issue, I would like the Summary to include some text and either CustomDate1 or CustomeDate2, whichever field has a value as the other field will be null.

Bill Sheboy

Hi @David Quiram

Yes, and...to what Jack suggests:

If one is *always* null, just put them side-by-side and one will disappear, without the extra delimiter: {{issue.summary}} - {{issue.firstDate}}{{issue.secondDate}}
Otherwise, you could use the conditional logic to do this in-line or use if/else components for extra testing: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/

I recommend #2 as *always* may be difficult to enforce/remember.

Kind regards,
Bill

Jack Brickey

You can add an if/else condition to check one of your date fields for empty and if empty then use the other date, if not the use that date.

now what I find worrisome is the fact that you could have a date in both so I think you need to consider this in your automation to help flag this apparent error condition.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

atl-gruland

automation