youngmon/atlassian-qna huggingface dataset:
Automation changing a ticket status
Asked by Danielle David:

Hi trying to do an automation to say if a ticket is in the status "Pending Business" and if not moved for 2 days then an automation to move to "Done Rejected"

i Have set up the below, but just not changing the status.![image.png](/t5/image/serverpage/image-id/331319i21C93C9038AD1FF9/image-size/large?v=v2&px=999 "image.png")

project = DAM AND status = "Pending Business" and updated \< startOfDay(-1)


Answers:
author: Jerrold - Empyra
body: Hi [@Danielle David](/t5/user/viewprofilepage/user-id/4577696)

Can you please check whether the transition has any validators or conditions in the workflow and Can you also check if the actor of the rule has transition issue permission in the project

Can you please share the error message you are getting in this automation it will be helpful to identify the issue more clearly

Thank you.

comments: author: Danielle David
body: Hi Jerrold,

No restrictions on the conditions or permission.

In the logs of the automation it has No Actions Performed with the below message.

##### [Scheduled](https://mirvac-sandbox-643.atlassian.net/jira/servicedesk/projects/DDM/settings/automate#/rule/19982766/473212755) {#toc-hId--1450151892}

No related issues that have been updated since the last time this rule executed could be found. To include all issues, un-check the 'Only include issues that have changed since the last time this rule executed' checkbox.


author: Jerrold - Empyra
body: Hi [@Danielle David](/t5/user/viewprofilepage/user-id/4577696)

Sorry for the late reply can you please uncheck the "Only include issues that have changed since the last time this rule executed" checkbox in the trigger

![ac.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/331815iF695056EE5F398A0/image-size/large?v=v2&px=999 "ac.PNG")

Please un check this and try running your automation.

Thank you.


Tags: cloud

jira-service-management

jira-service-management-cloud
JIRA Service Management - Confluence Integration
Asked by Emirhan T?rkay:

Hi!

I want to follow a process within the company on JIRA. I created a document that teams can edit and I want them to edit it through confluence.

In the JIRA Service Management workflow, how can I automate the person who is assigned to one status to automatically switch to the other status when he edits through confluence?


Answers:
author: Anusha A
body: Hi Emirhan,

Welcome to the Atlassian Community support and Thanks for your question!

After an internal review, I didn't find many cross-product triggers in Automation for Jira. I recommend checking out this feature request and sharing your use case to ensure our developers are aware of the customer needs. I agree that having a feature that allows automating the transition of the assignee from one status to another when editing through Confluence would be beneficial.

* <https://jira.atlassian.com/browse/AUTO-64>

I would request you to vote for the feature and add yourself to the watcher's list to get updates from developers and product managers following our [Feature Policy](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html).

We hope that we were able to give a clear overview of the situation. If you consider that we still can help with this, please don't hesitate to get back with further questions. We will be happy to help!

Regards,  
Anusha A


Tags: cloud

jira-service-management

jira-service-management-cloud
Loop through Fixversion that is attached to an issue and show all issues in that fixversion
Asked by Larry Katz:

I can't seem to find this functionality.  

I have a rule that does the following:  

trigger: Issue Transition to "Ready To Deploy" from any status  

when triggered it  

closes the attached Fixversion on that ticket using the smart value: {{issue.fixVersions.name}}  

This works fine.  

But I also want to send an email and in the body of the email, with the same Fixversion that's attached to the above ticket, lists all tickets in that Fixversion in the email body.

I've tried a few combinations on this page, but nothing prints out the list of issues in a fixversion that is attached to the ticket that made the transition for the trigger:  
<https://support.atlassian.com/jira-software-cloud/docs/smart-values-lists/>


Answers:
author: Andreas Knecht
body: Hi Larry,

I believe you should be able to do this with our new "Lookup issues" action: <https://support.atlassian.com/jira-software-cloud/docs/automation-actions/>

So in your rule you can add this:

* Trigger: Issue transitioned
* Action: Release fix version
* Action: Lookup issues and search for fixVersion = {{issue.fixVersions}}
* Action: Send e-mail and use the new {{lookupIssues}} smart-value:

```
Just released:

{{#lookupIssues}}

? * {{key}} - {{summary}}

{{/}}
```

This would print a bulleted list of all released issues. Hope that makes sense.

Cheers,  
Andreas

comments: author: Magdalena Dessoulavy
body: Is {{#lookupIssues}} action also awailable for DataCenter?
Automation is set up to create new epic on transition I want to not create epic if 1 already exists
Asked by Jamie Gerace:

I**have an automation set up:**

When transitioned to: In Progress

Create: New epic

**What I want:**

When: Transitioned to In Progress

Create: New epic

When: Transitioned BACK to "In Progress"

If: Current issue has already created a epic, do not create another

***Note:*** *Outside of limiting the transition to lock step, I can't figure out how to NOT create another epic if the issue is transitioned back to "In Progress" after moving out of it.*


Answers:
author: Andreas Knecht
body: Hi [@Jamie Gerace](/t5/user/viewprofilepage/user-id/3788098) ,

That should be possible, but you'll have to establish some kind of link or you'll need some kind of criteria to find the already created epic.

You'll have to change your rule like this:  

* Trigger: Issue transitioned to inprogress
* Related issues condition: Here's where you can search for the epic issue (if it's linked, you could look through linked issues, or you can just use JQL). Then set the condition to check that this issue \*Doesn't exist\*
* Create the epic

For more info see the 'Related issues' condition on <https://support.atlassian.com/jira-software-cloud/docs/automation-conditions/>

Hope that helps!

Cheers,  
Andreas
Adding "Linked issue" automatically
Asked by Steffen Vester:

Hi community..

I recently started using Atlassians app "Automations for Jira", and I read a lot about it, read the user cases etc., but I can't figure out how to do this:

I want to create an automation that will add a specific "relates to" linked issue, to all new issues that matches my JQL.

So whenever a new Epic is created, in a certain project and with certain details, it should automatically link that new Epic to a specific issue, e.g. TST-1350.

I have attached the screendump that I'm working on, and in the description it says "You can link to the issue that triggered this rule, previously created issue, a smart-value or simply an issue key.". But as you can see in the dropdown (attached screendump), theres only the first two mentioned possibilities.

I also tried working with JSON, to see if I could get it to automatically add a linked issue to that certain issue I mention above. But I'm not into coding, so that didn't work out.

Can anyone help me with either how to selecting which issue key it should link to, or to write JSON code that does the trick?

Thanks in advance!

![Automations for Jira.png](/t5/image/serverpage/image-id/100070i5D9F29E8F974FD9C/image-size/large?v=v2&px=999 "Automations for Jira.png")


Answers:
author: wwalser
body: Hi [@Steffen Vester](/t5/user/viewprofilepage/user-id/2965487) I believe you should be able to simply type an issue key into that field. When you begin typing, the dropdown item will change from a pre-filled suggestion to "Create new {{issue key}}".

Let me know here if that works out.

Also, if you're thinking that the "create new" label is a confusing, I agree. I'll look into getting that changed to something clearer.

comments: author: Steffen Vester
body: [@wwalser](/t5/user/viewprofilepage/user-id/346930) woooow thanks, that was easy. I didn't realise the field was an input field. I tried so many different things and methods, so yeah it could be clearer :)

Thanks a lot.


author: wwalser
body: <https://codebarrel.atlassian.net/browse/AUT-1979> Tracks the field label clarification.


author: Steffen Vester
body: [@wwalser](/t5/user/viewprofilepage/user-id/346930) perfect!

Now that I found an expert, can you tell me if it's possible to edit an existing "linked issue" value rather than creating a new one?

So if I in an automation rule that say when a new issue is created, allways link it to Issue A.

When the issue transitions to status "Done", then link to issue B instead. I don't want to create a second issue link, I want to edit the existing issue link to a new value.

Do you know if this is possible?

Thanks in advance


author: wwalser
body: Instead of "editing" the issue link, you'll probably need to use two separate actions on the automation. One to delete the old link (A) and a second to create the new link (B).


author: Steffen Vester
body: Off course. Thanks


Tags: issue-link
Story Points is not 0 by default - is null - Drop down is expecting an integer
Asked by Jorge:

Hello,

I want to setup the following business rule: when a task or story transitions to "In Progress" and has no story points to notify the slack channel.

When I set the condition to check for storypoints the only option is a number starting from 0, But when a task is created or a story the storypoints field is blank or null. So the condition if storypoints = 0 will never be true because will be null when a user created a task and forgot to include the storypoints.

Is there a way to include null in the drop down of possible values, that way we can compare with Null or Zero to cover two possible scenarios?

Thank you,

Jorge


Answers:
author: Jane Yeoh
body: Hi Jorge,

Thanks for reaching out. You can use our Issue Field Condition to check if Story Points is empty. I've attached a screenshot of what your rule might look like:

![Screen Shot 2020-06-22 at 9.20.02 am.png](https://community.atlassian.com/t5/image/serverpage/image-id/99829iC530C21F1527EC14/image-size/large?v=v2&px=999 "Screen Shot 2020-06-22 at 9.20.02 am.png")

Let me know if you need any more help with your rule.

Kind regards,

Jane (Automation for Jira)

comments: author: Jorge
body: Thank you! That works perfectly! :)


author: Jane Yeoh
body: Hi Jorge,

Glad to help! Feel free to reach out if you need further help.

Kind regards,

Jane
Impossible to updating required field value on issue creation?
Asked by David J:

Hi all,

I've run into the following issue and wondering if anyone has ideas how to overcome it:

Use case: on creating (or editing) an issue, I want automation to listen for the user changing a mandatory radio button field, and once it is being changed, I want automation to take the value of a number field A, and populate another number field B with it.

In my tests I faced the following:

1. this calculation cannot trigger before the issue is created

-\> acceptable to calculate upon submitting an issue creation (and not applicable on edit as the issue exists), we can document that.

2. this calculation does not trigger/execute because before it comes to that, Jira throws an error of field B being required, before Automation can populate it.

-\> is there a way to give Automation priority over the "required" field check?

-\> any other ideas?

Thank you all in advance!

David


Answers:
author: Benoit
body: The way Automation works, it's impossible!
Hi I am a JIRA user but new to JIRA automation. I am planning to create project to verify results
Asked by Manasa_Kp:

As mentioned in description, I am planning to create a JIRA project where I need the results(new task) to compare the data between already existing filter with the local network drive and then pop the results. Please assist

Regards,

Manasa


Answers:
author: Benoit
body: Please explain more. I am not sure of what you are trying to do.

comments: author: Manasa_Kp
body: I am trying to create a filter or report where I will be comparing data in the JIRA filter with local copy(data saved in network drive) .. Is it possible to create any filter as such??


author: Benoit
body: If you use external data, I don't see anything native from Jira that can do that.
How do I properly use strings in a "For JQL" automation rule when using smart values?
Asked by Eric Masyk:

Jira/Apps Versions:

* Jira Server: 8.8.1
* Automation for Jira: 7.1.14
* JQL Search Extensions: 3.1.3

Description of the automation which I want to accomplish:

* Trigger: On change of "Customer Name" field
* For JQL: "Customer Name" \~ {{issue.Customer Name}}
* Then: Edit issue and copy "Customer Name" from "Trigger issue"

The automation is triggering properly, and it's correctly finding the "Customer Name" field, which in my test case, contains the string "ACME INC, Co." This breaks the automation because there are spaces in the name (see error below). Since the field I'm wanting to match is a free text field, it will always contain a string (name) with a varying number of spaces, special characters, lengths, etc.

Below is my error, which to me is obvious that I need to somehow create the "For JQL" search to treat the "Customer Name" as a string, but for the life of me I cannot find any documentation on how to accomplish that:

* TIX-439: "(("Customer Name" \~ ACME INC, Co.) AND (key != TIX-439)) AND (project in (redacted))" - Error in the JQL Query: Expecting either 'OR' or 'AND' but got 'INC'. (line 1, character 31)

How do I make the Jira automation wrap ACME INC, Co. in quotes so it treats it as a text string? TIA!


Answers:
author: Eric Masyk
body: I found a colleague who had the same issue but figure out the solution, so I'm putting it here for others, and it's quite simple:

Wrap your smart value in quotes, OUTSIDE the braces. FWIW, I did everything BUT that... Not sure why this isn't clearly documented anywhere, my colleague had the same issue finding an answer, and stumbled upon it by brute force trial and error...

Example: "{{issue.Customer Name}}"

comments: author: Petar Andreev
body: This was something I was banging my head on for so long. Thank you for sharing!
Jira Portfolio - Team field question
Asked by Tony Rossiter:

All,

My customer use case is to set the Team field to value 1215 when the issue is created if the Team field is left empty. I've tried a couple of different approaches but none is working as hoped:

#1 - Edit Issue Fields

![Screenshot1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/98311iC30D1260AFC453C0/image-size/large?v=v2&px=999 "Screenshot1.jpg")

#2 - Set Entity Property

![Screenshot2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/98312i62A33FEF7E8D6608/image-size/large?v=v2&px=999 "Screenshot2.jpg")

Neither is working.

Any ideas? Happy to share Audit Log messages as needed.


Answers:
author: Julian Antu?a
body: Hi! This is what we did and works perfectly (you need to check the id of the tempo field first)

![team field.png](https://community.atlassian.com/t5/image/serverpage/image-id/109879iC81366BEAF95D910/image-size/large?v=v2&px=999 "team field.png")

comments: author: Ruben Dewyngaert
body: Shame it's hard-coded, but it works like a charm, thanks!


author: Craig Johnson
body: Tony,

You almost had it with the first example above.

I got this working using your first example, however I needed to change from using "When issue created". Instead, I used "When: Value changes for" changes to the Summary field (and for All issue operations).

Reason for this is that the issue key doesn't exist when the Edit issue field was firing.

Hope this helps.

Craig


author: Sarah Oros
body: If this is the Team field managed by Portfolio - I've also had no luck. I was hoping to see if I could customize subtasks automatically generated based on team since there are multiple teams working on the same project.

I noticed some other Portfolio fields are unable to be used with the Issue Fields Condition options - Epic Link, Parent Link aren't available. These custom fields are LOCKED in the admin list of fields.
How can I set the a date of an issue based on the earliest/latest date of related issues?
Asked by stringsonfire:

I'd like to:

1. Take a main issue
2. And when it's sub-tasks or linked "is blocked by" issues have a field change on "Start Date" or "End Date"
3. Find the earliest "Start Date" and latest "End Date" of these issues
4. Apply the Earliest Start Date and Latest End Date to my main issue

Is this possible?


Answers:
author: Elad Ben-Noam
body: Hi [@stringsonfire](/t5/user/viewprofilepage/user-id/1109351),

Sure, it's possible but you need to change the way you think about this. you will probably need to split the sub-tasks and the "blocked by" issues.

Your trigger should be "field value changed" for "start date", "end date".

filter for "sub task" types only.

then use "if-else" filtering

on the first if: add "Advanced compare condition" and compare {{issue.parent.start date}} greater than {{issue.start date}}.

if it passes, add a "branch" to "parent" and then add "edit issue" action to copy the start date from the trigger issue.

Then use "else" to check for "end date" the same.

If it works - create a 2nd automation for blocked issues (you can probably merge the 2 automation but it will require much more filtering)

That should work. Good Luck!


Tags: date

schedule
Jira Automation Rule To Update Statuspage
Asked by Michael Brizic:

I would like to create a Jira Automation Rule that when triggered the action is to create an incident in Statuspage.io

Is there a way to create an incident in Statuspage.io for a Jira Automation Rule?


Answers:
author: Bill Sheboy
body: Hi [@Michael Brizic](/t5/user/viewprofilepage/user-id/1589979)

Have you solved this question already? If not, please review the various integration options on this documentation page. It seems like you could use either the email or Jira integrations to solve this from Jira automation rules.

<https://support.atlassian.com/statuspage/docs/automate-actions-with-integrations/>

Best regards,

Bill


Tags: jira

status
How can I iterate through a multi-select field in an Automation for Jira flow?
Asked by stringsonfire:

Hi

I have a multi-select field called "Teams". When the issue reaches the "Ready for Dev" stage, I want to create a subtask for each option selected in "Teams", populating a single select "Team" field in the sub-task.

Is there a way to iterate through the selected items in the "Teams" field, and run a branch for each selection? I'd also need a custom value to set the single-select Team field to, like {{multiselect.iteration}}.

Thanks


Answers:
author: Elad Ben-Noam
body: Hi [@stringsonfire](/t5/user/viewprofilepage/user-id/1109351),

There is a way that I found, but I'm not sure this is the easiest.

When the status = "ready for dev" run:

if "Teams" not empty -\> "create issue" and populate the "Team" field with the smart value {{issue.Teams.first.name}}

on the more options, add the following:

```
{
  "update": {
    "Teams": [
    {
      "remove": {
        "name":"{{issue.fields.teams.first.name}}"
      }
    }
    ]
  }
}
```

You can use "re-fetch issue data" and continue the rule if there are more "Teams".

The other option is to change a different field so it will run a different automation rule as long as "Teams" is not empty.

If you don't want to lose the "Teams" field content - you'll need to first copy it into a different field.

comments: author: t0mhAn3110
body: Hi [@Elad Ben-Noam](/t5/user/viewprofilepage/user-id/2466213)

Similar to the case above, I have a scenario where I want to create issues on a particular transition. Here instead of Teams i have a multi-user field as "Stakeholders", and for each stakeholder added in this field, I want to create that many number of issues. Till here everything works fine.

The issue is that additionally I also want to set the "Assignee" of each newly created issue to each value in the field "Stakeholder".

I tried this:

![Screenshot 2021-10-27 at 14.20.57.png](https://community.atlassian.com/t5/image/serverpage/image-id/166761i37EC649E55BACA30/image-size/large?v=v2&px=999 "Screenshot 2021-10-27 at 14.20.57.png")![Screenshot 2021-10-27 at 14.22.02.png](https://community.atlassian.com/t5/image/serverpage/image-id/166762i2F166C671F39DB36/image-size/large?v=v2&px=999 "Screenshot 2021-10-27 at 14.22.02.png")

However, seems that I am missing something.

Could you please help :)


author: Jeff Henderson
body: Hi [@t0mhAn3110](/t5/user/viewprofilepage/user-id/4596967) ,

Did you ever find a solution to this? I'm trying to iterate through a multi user field to assign them to a new subtask as well.
For posting to Slack, is the icon associated with the action customizeable?
Asked by David Kaplan:

Hi,

Would like to customize the icon associated with the Automation action  
Is this doable?

thanks,

David  

just seeing the lightning bolt at the moment

![automation.png](/t5/image/serverpage/image-id/97797iC8B454935499BCC2/image-size/large?v=v2&px=999 "automation.png")


Answers:
author: Dee
body: Hi David,

try unchecking "Send message as Automation for Jira" in the Send Slack message rule component in the   
***Project settings \>\> project automation***

![Screen Shot 2020-06-17 at 9.45.44 am.png](https://community.atlassian.com/t5/image/serverpage/image-id/99219iD03ED45432B7E89D/image-dimensions/590x337?v=v2 "Screen Shot 2020-06-17 at 9.45.44 am.png")

then in the slack app settings of your Incoming WebHooks set a custom icon![Screen Shot 2020-06-17 at 9.48.05 am.png](https://community.atlassian.com/t5/image/serverpage/image-id/99218iF7335EE8A62F28EA/image-dimensions/592x267?v=v2 "Screen Shot 2020-06-17 at 9.48.05 am.png")

TIL

there seems to be a way to set the app name and icon from the json of the rule also check this out:![Screen Shot 2020-06-17 at 9.54.24 am.png](https://community.atlassian.com/t5/image/serverpage/image-id/99217i31D2E05C12D62196/image-dimensions/600x149?v=v2 "Screen Shot 2020-06-17 at 9.54.24 am.png")


Tags: icon
Update field with assignee of parent issue
Asked by Mark Wheeler:

Hi there

I've created a Project Automation rule to create a new sub-task when certain conditions arise.

If a new sub-task is created then I would like to set a custom field, which is of type "User Picker (multiple users)" to the value of the Assignee of the parent issue.

I believe I need to use the "More Options" ... "Additional Fields" feature in Project Automation to do this.

I've tried the below and many other variations to get this logic working but no work. Could someone put me out of my misery and help me if the JSON please ... so set a custom field to the value of the assignee from the parent issue, when the sub-task is being created.

{  
"update": {  
"customfield_10394" : \[  
{  
"add": {  
"id":"{{issue.parent.assignee.key}}"  
}  
}  
\]  
}  
}


Answers:
author: Elad Ben-Noam
body: hi [@Mark Wheeler](/t5/user/viewprofilepage/user-id/3163878) ,

There is no need for "more options" section.

you add the relevant field on the "edit issue" screen, then select from the three dots on the right side of the field to copy from and then select to copy from "parent" the "assignee" field. see images.![ans_2.png](https://community.atlassian.com/t5/image/serverpage/image-id/99502i0EDD4653544D8D27/image-size/large?v=v2&px=999 "ans_2.png")![ans_1.png](https://community.atlassian.com/t5/image/serverpage/image-id/99503i3FD20EC190BDE235/image-size/large?v=v2&px=999 "ans_1.png")

I hope it helps.


Tags: assignee

hierarchy