youngmon/atlassian-qna huggingface dataset:
Automate sprint goal?
Asked by Nicola:

Hi There,

Is it possible to set an automation so that when a sprint is started, the sprint goal becomes populated?

We have a regular (operational ) sprint goal that we quite often forget to include amongst other higher priority sprint goals.

Having an automation in place will help with this.

Thanks in advance!

Nicola


Answers:
author: Sebastian Krzewi?ski
body: Hi [@Nicola](/t5/user/viewprofilepage/user-id/5299475)

What you can do is to use 'Send web request' action and update sprint via rest api.

Example for Jira Cloud - <https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-rest-agile-1-0-sprint-sprintid-put>

Example for Jira DC - <https://docs.atlassian.com/jira-software/REST/9.12.0/#agile/1.0/sprint-updateSprint>

Regards,

Seba

comments: author: Nicola
body: Thanks for this. I am not entirely sure how to use this, but I will find someone who does to work together on the automation rule. thank you!


author: Bill Sheboy
body: Hi [@Nicola](/t5/user/viewprofilepage/user-id/5299475)

Adding to the other answers...Here is a how-to article for calling a REST API function with the Send Web Request action in a rule:

<https://community.atlassian.com/t5/Jira-Software-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828>

Kind regards,  
Bill


author: Nicola
body: .


author: Mark Segall
body: Hi [@Nicola](/t5/user/viewprofilepage/user-id/5299475) - Not natively. However, there may be a way to leverage the Jira API via the Send Web Request action.
automate comment after ticket doesn't have any activites after x amount of time e.g. 24 hours
Asked by conrad_w:

Hi, I'm looking to see if it is possible to create an automation rule in which when the condition below are met as example:

1) user submitted a ticket to X-Project

2) tech is assigned to the ticket

3) upon reviewing, the issue require additional time to be resolved

4) while pending resolution, the tech forgot to provide update/comment to user after 48 hours.

from the above scenario, I would like to know if it is possible to create an automation rule in which Jira scan for all open tickets assign to a tech, and look for ticket that has no comment or activities past 24 hours, and inserted with a "generic text". Knowing that Jira logs this under Activity of the ticket, so I think it is possible. Just that I don't know how to create this automation. Appreciate any help you guys can provide.


Answers:
author: Asha Goyal
body: Hello [@conrad_w](/t5/user/viewprofilepage/user-id/5419592)

This Automation can help you, feel free to change the period as needed:

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

In addition to this you may want to reopen the ticket if someone comment on the ticket:

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

Kindly Accept and Vote if it helps.

Thanks

comments: author: conrad_w
body: thank you AG, appreciated the tips. Will have a look.


author: Bill Sheboy
body: Hi [@conrad_w](/t5/user/viewprofilepage/user-id/5419592) -- Welcome to the Atlassian Community

Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community offer suggestions.

Thanks, and kind regards,  
Bill
Sub-Tasks
Asked by Nils Hornitschek:

I want in a process that if the sub-tasks are not filled with text, I cannot move on to the next workflow step.


Answers:
author: Bill Sheboy
body: Hi [@Nils Hornitschek](/t5/user/viewprofilepage/user-id/5345542)

That cannot be done with an automation rule (and you have posted this question in the automation area).

Instead please consider using a workflow validator for the field: <https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Validators>

Kind regards,  
Bill
Automation for Jira user creation
Asked by Rolo:

Is there a way to create users automatically? I want to create a board where issues are created with user creation requests and when issues are in a certain state they are sent to create automatically


Answers:
author: Rebekka Heilmann _viadee_
body: Hi [@Rolo](/t5/user/viewprofilepage/user-id/2167448)

a User cannot be created per Automation rule itself (Automation can't even assign Users to a project role), but you could call the Jira API from a rule with a "Send Web Request" Action. The "create user" request is experimental but exists: [The Jira Cloud platform REST API (atlassian.com)](https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-users/#api-group-users)

comments: author: Bill Sheboy
body: Hi [@Rolo](/t5/user/viewprofilepage/user-id/2167448)

Just checking if this answered your question. If so, please mark this one as "answered" to help others find solutions faster. If not, provide any additional information to help the community offer suggestions.

Thanks, and kind regards,  
Bill


author: Kieren _SmolSoftware_
body: To add to [@Rebekka Heilmann _viadee_](/t5/user/viewprofilepage/user-id/5182395)'s answer. The user would also have to be put into a group that granted them product access, as just creating the user isn't super useful. This could be done by calling one of the Jira APIs.
How to automate Group_cc?
Asked by yirang Im:

Hello! I am not sure if this community is right place for my issue.

I am setting JIRA Project for my team and need help in setting Jira Automation.

I want to make it put "Group_CC" automatically when an issue is created as many people don't fill that field very often.

So, my automation setting is following, but it doesn't work.

1. When : Issue created

2. If : Linked issues match  
Types : All link types Match : "epic link" in (A)

3. Then : Edit issue fields  
Group_CC

I understood like if the issue being created has any link with "epic link" in (A), then put Group_CC. But it is not working. What I am missing?

Thank you very much!


Answers:
author: Bill Sheboy
body: Hi [@yirang Im](/t5/user/viewprofilepage/user-id/5355122)

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...

What version of Jira are you using: Cloud, Server, or Data Center?

What is the scope of your rule: project, multi-project, or global?

In which projects are the issues you are checking: one project or multiple projects?

There are different versions of automation for different Jira versions, leading to different behaviors.

And, if your issues span different projects, the scope of the rule impacts the behavior.

Kind regards,  
Bill


Tags: jira
Sum Up Story point estimate onto epic (parent) from child issues
Asked by Franziska Beckert:

Hi there,  

I've been trying all kind og approached documented in the Atlassian community on how to sum up the story points, stored in a custom number field calles "Story point estimate" onto the parent which is an epic. As children of epics we use two issue types "Task" and "story".   

I can't get the automation to sum up all values of the child tasks and stories into an other custom field on the parent (epic) called story point actual.  

Can you please help me.   

<br />


Answers:
author: Bill Sheboy
body: Hi [@Franziska Beckert](/t5/user/viewprofilepage/user-id/5415550) -- Welcome to the Atlassian Community!

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...

What type of project are you using: team-managed or company-managed? You may find this information at the bottom-left side of the page's expanding area.

Team-managed projects use the "Story point estimate" field and company-managed ones use "Story points". If the incorrect one is used rules may not work as expected.

Kind regards,  
Bill


author: Kalyan Sattaluri
body: Hello, Welcome to the community.

There have been many discussions around this requirement on this forums, below are few for example.

<https://community.atlassian.com/t5/Jira-Software-questions/Automation-I-am-looking-for-a-way-to-sum-Story-points-for/qaq-p/1647852>

<https://community.atlassian.com/t5/Automation-questions/Sum-up-Story-points-to-epic/qaq-p/1389224>

Please share a screenshot of what you have implemented so far for us to help faster.
Which tool for Capacity Planning the Automated Time Tracking?
Asked by Gil:

Hi everyone,

My team decided to use Capacity Planning in our Scrum process and I'm trying to figure out which Jira addons are recommended for this job, while also tracking the time spent on their work.

I'm looking for tools who provide as much automation as possible, since I cannot trust people to remember to manually measure how much time they spent on a give task in Jira.

I've seen many tools in the marketplace, but I'm asking the community for your insights and what has worked best for you.


Answers:
author: Amay Purohit_RVS
body: Hi [@Gil](/t5/user/viewprofilepage/user-id/1264836)

If you are looking for a mktplace app to help you to plan the capacity for your team members and track them, you can try out the one we have developed for the same use case.

[Capacity Planner](https://marketplace.atlassian.com/apps/1231411/capacity-planner?hosting=cloud&tab=overview%20)

The app allows to store the capacity for individual users and save as templates. which can be mapped to a sprint / fix version to track the allocation and remaining time per user. Do try it out.

Disclaimer : I am part of the team which developed this app

![Sprint Capacity-new.png](https://community.atlassian.com/t5/image/serverpage/image-id/302925i353ED2425CB670CA/image-size/large?v=v2&px=999 "Sprint Capacity-new.png")![TeamMember_Tasks.png](https://community.atlassian.com/t5/image/serverpage/image-id/302927iDBDE6BCD1A4A003A/image-size/large?v=v2&px=999 "TeamMember_Tasks.png")

comments: author: Gil
body: thanks for the reply


author: Bill Sheboy
body: Hi [@Gil](/t5/user/viewprofilepage/user-id/1264836)

I have not used any addons for capacity planning for any teams I've supported...mostly because different teams do this in different ways. And so we have usually done it just-in-time as part of sprint planning and / or with a simple spreadsheet.

My recommendation would be to jot down some notes (with examples) of what you do today and what your team's "wish list" would be to help automate that. Then install some of the marketplace addons as trials to learn which ones help.

Kind regards,  
Bill

comments: author: Gil
body: Thanks for the reply


Tags: app

capacity

jira

jira-software

plan

time-tracking
Getting 408 Error When Sending Web Request to Adobe Workfront
Asked by Patrick Cook:

Hello,

We're trying to setup some automations with our service desk, and with that we're trying to send a web request. When sending this web request, we mainly get a 408 error (NoHttpResponseException: The target server failed to respond), though I have seen a (I think) 422 sock error. With that in mind, we reached out to our Workfront support team with this issue.

For context, I sent a request from Jira and then I **sent the same exact request** (with the same headers) from my computer using Postman and also from Power Automate in our Microsoft 365 tenant. My computer and Power Automate were successful, but Jira was not.

When looking at the logs, they saw our successful requests from my computer and Power Automate, but didn't see any trace of Jira, not even a block.

Is there a default restriction perhaps or maybe somewhere we need to allow certain URLs/IPs for outbound web requests?

Here's our request: https://hidden.my.workfront.com/attask/api/v17.0/proj?name={{issue.properties."proforma.forms.i1".state.answers.64.text.urlEncode}}+%28{{issue.properties."proforma.forms.i1".state.answers.19.choices.urlEncode}}+Rooftops%29+%7C+New+Client+Setup+%7C+Starts+{{issue.properties."proforma.forms.i1".state.answers.59.date.urlEncode}}\&templateID=hidden\&portfolioID=hidden\&companyID=hidden\&ownerID=hidden\&groupID=hidden\&status=CUR

I did verify that the smart values do work and are sending correct values in the validation portion of the automation.

Thanks!


Answers:
author: Patrick Cook
body: Posting the answer back here in case anyone else gets stuck. Jira Automation doesn't like path parameters in POST requests, so any path parameters must be passed to the body. Make sure to add a header "Content-Type = application/x-www-form-urlencoded" and copy-paste any path parameters you have in a custom data body form. (and be sure to remove the question mark)

So in my case, the URL will be "https://hidden.my.workfront.com/attask/api/v17.0/proj" and the custom body will be "name={{issue.properties."proforma.forms.i1".state.answers.64.text.urlEncode}}+%28{{issue.properties."proforma.forms.i1".state.answers.19.choices.urlEncode}}+Rooftops%29+%7C+New+Client+Setup+%7C+Starts+{{issue.properties."proforma.forms.i1".state.answers.59.date.urlEncode}}\&templateID=hidden\&portfolioID=hidden\&companyID=hidden\&ownerID=hidden\&groupID=hidden\&status=CUR"
Create tickets in all projects that meet certain criteria?
Asked by Shawn Oster:

I need to create the same ticket in multiple projects and I'd prefer not to create a discrete Create Issue action for each project.

Ideally I could query on project details, something like:

```
for each project where project.category == "Feature Team":
  create issue
```

If that doesn't work using JQL or a filter:

```
for each project in (ABC, DEF, EBC):
  create issue
```

Pretty much anything except:

```
create issue in ABC
create issue in DEF
create issue in EBC
```

Any ideas?

Cheers,

Shawn


Answers:
author: Bill Sheboy
body: Hi [@Shawn Oster](/t5/user/viewprofilepage/user-id/5048285)

What version of Jira are you using? If it is Jira Cloud...

You could try creating a variable with the list of **projects' id values**, separated by commas, and then use an advanced branch to loop over those. In the issue create action, use the branch variable as the project key.

* action: create variable
  * variable name: varProjectList
  * smart value: 10010,10011,10012
* advanced branch
  * variable: varProject
  * smart value: {{varProjectList.split(",")}}
    * action: create issue, using {{varProject}}

I have not tried this, so I do not know if the issue will successfully create with a lop variable as the project key.

Kind regards,  
Bill

**UPDATE**: I changed the CSV list of project names to use the projects' id values and the rule worked as expected.

comments: author: Shawn Oster
body: Hey Bill, that was a great suggestion but unfortunately you can't use smart values as inputs to the project list, as you suspected.

Give the number of projects (30+) I think I'm going with a quarterly CSV import.

Thanks again for your help.


author: Bill Sheboy
body: Sorry, I should have tested first: this only works if the list in the variable is the project id values. I will update my earlier post :\^)


author: Shawn Oster
body: Bill, you are my hero!

For future generations, you \*can\* use either project ID or key, depending on how you set your "More Options".

```
{
  "fields": { "project": { "key": "{{projectKey}}" } }
}
```

I was getting stuck trying to set the project in the UI somehow, which obviously doesn't support smart values.

I dearly wish I could write actual code, and I was sorely tempted to write a lambda instead that used the REST API, but this approach allows me to hand off maintenance to our product folk instead.

Thanks again for your help, saved me a ton of time!

Cheers,

Shawn


author: Bill Sheboy
body: Well done!

I was using the dropdown field to set the project and did not try using the JSON edit for fields already shown in the Create Issue action, such as project and type. I suspect this technique would also support creating with the one-off issue types and status values in team-managed projects.
How to Track automations executions per type of issue and per project
Asked by T?rence LECROIX:

Hello,

We'd like to know how many automations have been executed for a specific issue.

The point would to be able to estimate an average automation for a specific type of issue in specific project from the creation of the issue until its closure.

Is someone managed to get this information ?

The audit log provided by Atlassian doesn't allow gather such information which would be very usefull in order to be able to control and manage properly automation executions.

Thanks in advance !


Answers:
author: Bill Sheboy
body: Hi [@T?rence LECROIX](/t5/user/viewprofilepage/user-id/3728276)

Short answer:

I do not believe that is possible, even for an individual Jira issue. A mitigation may be to accurately document your rule usage, such as in Confluence, to track which issue types teams anticipate could be impacted by rules; then use this documentation with the Global Rule Usage data to make decisions.

Longer answer:

There are several reasons this information may not be available for customer analysis...

The automation, audit log details available to customers show the issues accessed by rules...up to a limit. They do not show all of the issues in the UI when there is a large batch, as the list of issues is truncated in the log.

And at this time, there does not appear to be a public REST API function to export automation audit logs for external analysis. (Although without this API, is unknowable if the audit log does indeed contain the list of all issues accessed :\^)

Individual issues have history, and when a rule makes changes to the issue the change log notes that, referencing the rule actor. And so theoretically one could read the change history for each issue to determine rule impact. However, the default actor is the *Automation for Jira* user, but if any actors in rules have been modified the change history will not indicate the actions were from a rule.

With the changes to the automation packaging model, what counts toward the limits has changed. And so some things which access issues will not necessarily appear in the logs. For example, using the Send Web Request action to search for issues using the Jira REST API.

The mitigation I noted earlier, along with actively managing automation rule usage may help with what your teams are trying to observe.

Kind regards,  
Bill


Tags: jira-cloud
Turning Task into Child Task Based on Cloned Epic
Asked by Mayra Hernandez:

Hello!

Would appreciate your assistance here. I have a workflow that based on a transition from a "Task" ticket - it creates a closed "Epic"

How can I then turn the trigger issue into a child of the epic.

Example flow here:

![screencapture-myntr-atlassian-net-jira-settings-automation-2024-01-23-17_28_15.png](https://community.atlassian.com/t5/image/serverpage/image-id/302089i59D8B6C6635D922E/image-size/large?v=v2&px=999 "screencapture-myntr-atlassian-net-jira-settings-automation-2024-01-23-17_28_15.png")


Answers:
author: Bill Sheboy
body: Hi [@Mayra Hernandez](/t5/user/viewprofilepage/user-id/5412907) -- Welcome to the Atlassian Community!

To set an issue as the child of an epic, you may set that child issue's parent field to the epic's key. If the "Epic Link" field is still shown you may also use that in the edit issue action.

In your rule, you are creating two issues, thus it is unclear which one is the epic, so I am unable to provide any clearer guidance on how to link the issues.

What is the purpose of the branch to most recently created issue in the rule?

Finally, you note creating a "closed epic" and then linking the trigger issue to it as a child issue. Why do that, as the trigger is not yet completed?

Kind regards,  
Bill

comments: author: Mayra Hernandez
body: Hi Bill!

Thanks so much for your response. Currently, my workflow triggers an Epic (not closed, I misspoke there). Once the Task - is in a certain status.

Flow is:

\* Issue Type - Task is created manually

\* Task is transitioned to "Ready for Sprint" status

\* Automation runs from here to create an Epic from the Task

My issue is then making the trigger issue (the Task) a child of the newly created epic - I am having a hard time trying to figure that out if that is possible.

Thank you!

Mayra


author: Bill Sheboy
body: Yes, that should be possible. This is the minimum steps needed, so please add any others you need.

* trigger: issue transitioned
* action: create issue (for the new epic)
* action: edit issue (This will edit the trigger issue.)
  * select the Epic Link field
  * enter this smart value {{createdIssue.key}}
  * when that appears below the field, select it to use the smart value

I see your rule was also editing the Original Estimate field. If that is still needed, I recommend doing it at the same time the Epic Link is set.


author: Mayra Hernandez
body: That worked, thank you so much!


author: Bill Sheboy
body: I am glad to learn that helped. Please consider marking this one as *answered* to help others find solutions to similar needs faster. Thanks!
Groovy formula - JMCF Calculated duration field
Asked by Sandy Greenberg:

Could someone please help me with a Groovy script to calculate the age of an issue for a custom field using the JMCF functionality? This is on Jira Server if that's important.

"today's date" - "(Jira Field) created" = number of days

Thanks!


Answers:
author: Suprija Sirikonda _Appfire_
body: Hi [@Sandy Greenberg](/t5/user/viewprofilepage/user-id/5236605),

You can use the below Groovy script to get the number of days between issue created date and the current date:

```
new Date() - issue.get("created")?
```

Regards,

Suprija


Tags: groovy