youngmon/atlassian-qna huggingface dataset:
Jira field usage limitation for JSM Portal forms?
Asked by phil harman:

I have established a Jira Service Management (JSM) project using Data Center. When I go to add fields to the Jira form for the portal, I only have these options ... (1) Summary (2) Attachment (3) Linked Issues (4) Labels, (5) Assignee.

I have several custom fields I must use to gather the initial data to start and evaluate the request.

Is there a JSM configuration setting to allow me (I'm the Jira Admin) to add more Jira fields, including custom fields?


Answers:
author: Bhanu
body: Hi [@phil harman](/t5/user/viewprofilepage/user-id/721264)

JSM request types will allow all the fields on the create issue screen of the issue type associated with it. Make sure you have all the desired fields added to the create screen of the issue type that you associated with request type and then go back to the request to add them.

I hope that this helps!

comments: author: phil harman
body: The most helpful phrase in your response is ... to*make sure you have "* ***all the desired fields added to the create screen*** *" of the issue type.*

That is why I did not see those fields to select from.

Thank you so much for your quick response.


author: Bhanu
body: Glad it helped


Tags: data-center

jira-service-management

jira-service-management-data-center
Structure / Try to sum the story point for the issues children of an EPIC
Asked by agnes BOURLON:

Hi

I am using a formula for building a column that calculates the sum of the points for the US included in an EPIC

I built my structure with the following element :

\* Add issues belonging to epics

\* Insert issues: project = "xxxx" and summary \~ "AMC" and issueType=Epic

If I use the column story points / sum over sub-items, I got the sum of the children story points AND the story point if the parent (the EPIC) whereas I would like to get only the sum without the Epic Story point.

In the column formula the following formula gave me no result.

SUM#children{"Story Points"}

I see that the COUNT#children{"Story Points"} gives me the number of tickets getting story points. But the SUM doesn't seem to work...

Is that a bug?  
Many thanks in advance for helping me,

Agnes


Answers:
author: Kelly Arrey
body: I'm on Structure Cloud, and this syntax was accepted:  

SUM#children{storyPoints}

but this syntax was not:  

SUM#children{"Story Points"}

Hope this helps :fingers-crossed:

comments: author: agnes BOURLON
body: Yes ! It works !! Many thanks

To be honnest I tried also SUM#children{StoryPoints} but it was wrong when I wrote the message.

Today both SUM#children{StoryPoints} and SUM#children{storyPoints} (with uppercase or lowercase for the first letter) =\> all work !  

Well, that's ok so :-)


Tags: expr

formula

structure
Sum up custom field value from all Epic issue types to Initiative
Asked by Asma Sultana:

Need your inputs as I am trying to sum up custom field values from all Epic to Initiative, similar to story points.


Answers:
author: Asma Sultana
body: ![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/239052iB955F5CEFCCF9627/image-size/large?v=v2&px=999 "image.png")

comments: author: Erin Quick-Laughlin
body: Hi [@Asma Sultana](/t5/user/viewprofilepage/user-id/5141492) - is the job working as expected so far? What kind of input / feedback are you looking for?


author: Asma Sultana
body: Not working in audit log it says success but in actual it's not summing up on parent issue type. Can you help me with the automation is any changes needed on script it would be same functionality as story points being calculated under Epic.


author: Erin Quick-Laughlin
body: I'm not sure what 'same functionality' means, but here's a few things to look at, depending on where you think the error might actually be. I don't know that this is the best way to make these work, but it's working for us on a similar field.

* Is Feature Points a number field? I believe it will need to be, to use **sum**
* Is it failing at the Lookup Issues? Try changing the Lookup Issues action to **"Parent Link" in ({{issue.parent.key}})**
* Is it failing at the Branch? also try changing "For Parent" to For JQL, using **issuekey = {{issue.parent.key}}**
* Is it failing at the Edit Issue? Try just selecting the field in the drop down, choose SET from the ellipses from the right of the field, and then copy **{{lookupIssues.Feature Points.sum\|0}}** in for the value.

Hope this helps!


author: Pourush Kalra
body: The problem with this approach is that it only takes 100 child issues at a time, and gives false values if \>100
How do I automate transitioning an issue when a specific user comments?
Asked by Adam Chapman:

We have an integration with Zendesk for support tickets, and sometimes we request more information for a ticket, so we transition this ticket to "Blocked". I would like to automate that when the 'Zendesk Integration for Jira' user updates the ticket, that it is then moved back to status 'New'.

What would be the best way to do this?


Answers:
author: David A
body: Hi Adam,

I think the best way is through Automation.

* Trigger:

When the commented issue

* Condition

User Condition: user perform 'Zendesk Integration for Jira'

* Action

Transition issue to New Status

Best regards
Is it possible to auto update master on release?
Asked by Chauncey V. Loving:

Hello, I was just curious if it's currently possible to set an automation up that would automatically bring our master branch up to date after a version is released in jira.

Say we're using version 1234, and we mark it released.

Maybe we then use regex like (version\\/{{version.name}}) to find our version branch in source tree.

I'd then like to auto create a pull request to merge the version branch into master, and have it approved automatically.

Does something like this exist as an automation option in jira?


Answers:
author: Jehan Bhathena
body: Hi [@Chauncey V. Loving](/t5/user/viewprofilepage/user-id/5113778) ,

Dont think that there is a solution for this out of the box, you can try the below steps:

1. Trigger: Version released
2. Action: Create a Smart Value with the version name, and append the content you wish too
3. Action: Webrequest : Use the Gitlab/Github API call to create merge request
4. Action: Use the above Webrequest's content in this step, and mark the above merge request as Merged
   1. PS: You may want to be aware of merge conflicts that may occur as well
Release Created - Automation Trigger??
Asked by Tommy Augustine:

Hi Community,

Is there a trigger out there (or in the works) for when a Release Version is created? I only see the "Version Released" trigger, but I think that's the Version's Release Date.   

I am trying to set up an automation that will copy a Release Version to specific projects when it is created in the project the automation is triggered from.


Answers:
author: Tommy Augustine
body: I am answering my question because I am blind. The "Version Created" does exist in Jira Automation. For some reason, it did not render for me when I looked in there earlier. Most likely a User Error on my part:  

![VersionCreated.png](https://community.atlassian.com/t5/image/serverpage/image-id/238505i98F8BAEB258F57FF/image-size/large?v=v2&px=999 "VersionCreated.png")
How to create automation rule from JIRA form to automatically calculate priority scores
Asked by Swati Sharma:

Hi All,

I am new user to JIRA.

While a form is getting filled in JIRA, its has fixed options in form of dropdown.

we have fixed numeric value assigned to every option selected and a formula to create priority score.

Out of the numeric values we manually calculate the priority score.

It can easily be automated as all the dropdown options has fixed numeric values. Please help me to create the automation.


Answers:
author: John Funk
body: Hi Swati,

You could try creating some variables in the rule and then use the variable to assign a numeric value for calculating.

comments: author: Swati Sharma
body: Thanks for the reply, I appreciate it. I have created the variables and provided numeric values, how to apply that in rule JIRA Automation. How to create the rule in JIRA Cloud.


author: John Funk
body: Can you share the rule that you have created so far?


author: Swati Sharma
body: this is the manual rule which we expect to be part of JIRA automated rule

|---|
|   |


author: John Funk
body: Can you screenshot the actual rule that you have built?


author: Swati Sharma
body: I am trying to build an automation or macro, that once the filed inputted and the form get submitted it automatically create the priority score.

Apologies, if I have created confusion but I want to know how to create the rule as I am struggling with rule creation in JIRA and not finding the relevant option.


author: John Funk
body: Take a look at this previous post to see if it helps you get started:

<https://community.atlassian.com/t5/Automation-questions/Automate-quot-Target-Date-quot-field-when-ticket-is-moved-to/qaq-p/2251838>

<https://community.atlassian.com/t5/Jira-Software-questions/Output-of-linked-tasks-using-smart-values/qaq-p/1646118>


author: Swati Sharma
body: Thank you


author: John Funk
body: You are welcome. I would love to see your finished, working rule when you get to that point. Also, feel free to ask more questions along the way to help get you there.


Tags: jira-cloud
Automation of JIRA requests
Asked by Melissa Darcey:

Hi all,

I'm new to this and am looking for help.

Currently, for work, we get a request through a web form and then need to manually create a JIRA for each request. Is it possible to automate the process so once a request has been submitted it will automatically create the JIRA request with the relevant information? If this is possible, can you please point me in the direction of any steps that may help me.

Thanks.


Answers:
author: Stefan Salzl
body: Hi [@Melissa Darcey](/t5/user/viewprofilepage/user-id/5139231) and welcome to the community,

in Jira there is a feature called "issue collector". You could embed this to your website and issue can be created via the collector. See link below:  
<https://support.atlassian.com/jira-cloud-administration/docs/use-the-issue-collector/>

Otherwise an issue could also be created via Rest API when the form of your website is submitted. This depends on your webform and how you store the data. Here is a link to the Rest API Docu:  
<https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post>

Hope this was helpful.

Best  
Stefan

comments: author: Darryl Lee
body: Yes to what [@Stef](/t5/user/viewprofilepage/user-id/869383) wrote. Also, there is a very powerful Forms function available in Jira Service Management, if you happen to have that available:

* [What are forms?](https://support.atlassian.com/jira-service-management-cloud/docs/what-are-forms/)


author: Charlie Gavey
body: Here's a little more info around the Forms [@Darryl Lee](/t5/user/viewprofilepage/user-id/1365322) mentioned, and how these can be used in Automation - <https://community.atlassian.com/t5/Jira-Service-Management-articles/4-New-Form-Automation-Components-for-Jira-Service-Management/ba-p/2018674>
Can i add an automation rule to assign release versions related to tickets/stories on the board?
Asked by Laura Njombua:

Currently we manually link or assign our release versions to the issue in question. Can we automate that process? thanks


Answers:
author: Mikael Sandberg
body: Hi [@Laura Njombua](/t5/user/viewprofilepage/user-id/5138372),

Welcome to Atlassian Community!

It is possible with automation, the question is do you want to do this association when the release is created or when the issue is created? The first one is the easiest one since you would trigger on version created. The second one would be a bit more complicated since the board is just a placeholder for issues and what you see on it is based on a filter. Your automation would trigger on issue created, then you would have to use [Get project versions](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-project-projectidorkey-version-get) and look if the version is released or not, and then set the version on the issue.

A third option if you associate all epics with a single release would be to copy that version from the epic when the issue is created and associated with an epic.
Adding value in request response to now
Asked by ?mer - OBSS:

Hi everyone,  

I'm trying to add the value from the rest response over the current date;  

To access the variable i am using;  

```
{{webhookResponse.body.table.body.rows.valueColumns.value.get(0)}}
```

This gives me a decimal number like 87.5 which represent hours.  

I need to add this value on current date with plusHours method. I tried many methods but i couldn't make it;  

```
{{now.plusHours( {{webhookResponse.body.table.body.rows.valueColumns.value.get(0)}} )}}
```

```
{{now.plusHours({{asNumber}}{{webhookResponse.body.table.body.rows.valueColumns.value.get(0)}})}}

```

```
{{#webhookResponse.body.table.body.rows.valueColumns}}{{now.plusHours({{value.get(0)}})}}{{/webhookResponse.body.table.body.rows.valueColumns}}
```

None of these methods work.  

On cloud i am using *Create Variable* action to assign this value on a variable but on datacenter *Create Variable* action not available. So I am trying to use access directly to variable.   

<br />

I'm open to all advice, thanks !  


Answers:
author: Bill Sheboy
body: Hi [@?mer - OBSS](/t5/user/viewprofilepage/user-id/3678185)

Once inside a set of curly-brackets you do not need to repeat them. Please try this:

```
{{now.plusHours(webhookResponse.body.table.body.rows.valueColumns.value.get(0).asNumber)}}
```

Kind regards,  
Bill


Tags: due-date

jira-server
Delete Jira issue property via Jira Automation
Asked by Rudy Holtkamp:

Hi,

With the action 'Set entity property' you can create a Jira issue property.

But is there a way to delete a property? Or is the only way to call the REST API?

Using this:

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/237842i669FE81379F2C1CF/image-dimensions/425x294?v=v2 "image.png")

Will result in:

```
{
  "key": "myproperty",
  "value": ""
}
```

Which means that the property still exists, but contains an empty string.


Answers:
author: Rudy Holtkamp
body: Yeah, I'm afraid that is true, couldn't find it myself.

For reference, use a sent web request with an authorization header, containing an API token:

```
DELETE {{baseurl}}/rest/api/3/issue/{{issue}}/properties/worklog_{{worklog.id}}
```


author: Bill Sheboy
body: hi [@Rudy Holtkamp](/t5/user/viewprofilepage/user-id/636802)

I believe that is only possible with the REST API from a rule. Here is a suggestion to add a delete action for rules: <https://jira.atlassian.com/browse/JSWCLOUD-22628>

Kind regards,  
Bill


Tags: jira-cloud
Is it possible to create an automation based on which board an issue is being created on?
Asked by Cary Lewis:

We have several teams all sharing the same project. Each team has its own board, with a custom filter to only surface tickets relevant to that team based on a component.  

I would like to create an automation flow where I can add a specific component based on which board the Create issue button is selected. Alternatively using the url would also work.  

Is there a way to do this?


Answers:
author: Bill Sheboy
body: Hi [@Cary Lewis](/t5/user/viewprofilepage/user-id/4474116)

Maybe...but not as how you describe it...

A board is a view of issues in a project based upon a filter. Automation rules cannot know about the "board" but you could determine if an issue matches a filter for a particular board, and take actions as needed.

IMHO: this is a risky rule unless your rule specifically uses the saved filter ids to confirm the board filters stay in synch with your rule logic.

Kind regards,  
Bill


author: Curt Holley
body: Hi [@Cary Lewis](/t5/user/viewprofilepage/user-id/4474116)   

I would do it like this....not perfect, but easy enough automation to write.

trigger = issue created

Condition = If/else block

Where if reporter is one of \[Insert all team members for the relevant team/component\]

Action: Edit issue to add the relevant team/component

Repeat for each team.

Yes!! the downside is, every time there is a team member change the rule needs editing.

<br />

Plus, the teams need to be appear this is occurring and if they want to create for another team they will need to add or edit the component field.

Bonus idea; You could add an initial (pre If/else) condition of "If Component is empty" so that if they configure it at creation. the rule will leave it alone.

comments: author: Cary Lewis
body: We had considered this approach, but in reality anyone on one team could create a ticket for another team, so this doesn't solve the problem.


Tags: component
Can I update the description field using an automation without clearing it?
Asked by Shanara Sadeque:

Hi,

I would like to set up an automation which generates a subtask. I would like the subtask to copy the description from the parent issue however I want to change some of the wording in the subtask. The parents issue contains text and a table in the description. Ideally I want the subtask to have different text but copy the table from the parent. Is this possible?

Thanks!


Answers:
author: John Funk
body: Hi Shanara,

Unless you can figure out a way to substring out just the table, you are not going to be able to copy just part of the field.
Filtering Approvers who approved with smart values
Asked by Rudy Holtkamp:

Hi,

I've been struggling for hours and hours, but can't find a way to get the names of approvers who approved an issue.

So we have a group of 10 users who are able to approve a certain issue. Only two approvals are required. When the issue is approved I want to make a comment in a linked issue stating that Person1 and Person2 have approved the linked issue.

So I've tried several ways of filtering the approvers, but none of them work. Note: customfield_10045 is the Approvals field. I would have thought that this should work:

```
{{#issue.fields.customfield_10045.approvers}}
   {{#if(equals(approverDecision,"approved"))}}
      {{approver.displayName}}
   {{/}}
{{/}}
```

But it does not give any output.

When I try this:

```
{{#issue.fields.customfield_10045.approvers}}{{approverDecision}}{{/}}
```

The output is:

```
pending, pending, pending, pending, pending, approved, pending, pending, approved, pending, pending?
```

Replacing {{approver.displayName}} with a string, does not output the string two times.

Hopefully somebody can tackle this.

Rudy


Answers:
author: Rudy Holtkamp
body: Thanks [@John Funk](/t5/user/viewprofilepage/user-id/7148) , though it is not the solution, the comments in the other posted got me on the right track. For future reference this is the solution:

```
{{#issue.fields.Approvals.approvers.get(0)}} 
   {{#if(equals(approverDecision,"approved"))}} 
      {{approver.displayName}}
   {{/}}
{{/}}
```

comments: author: Carlos Pe?afiel Juarez
body: Gracias por la aportaci?n

Si funciona.


author: John Funk
body: Hi Rudy,

Take a look at this previous post to see if it can help you. And maybe try {{issue.Approvers.displayName}}

<https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Automation-for-Jira-How-get-the-approver-value-Display-name/qaq-p/1412028>

comments: author: John Funk
body: Great! Glad you got it figured out.


Tags: cloud

filter

jira-cloud
Send an email when a customer has not responded in x amount of time
Asked by P?tur Bj?rn:

Hi

How can I close an issue automatically when a customer has not responded in an x amount of time?


Answers:
author: Samuel Gatica
body: Hi [@P?tur Bj?rn](/t5/user/viewprofilepage/user-id/3659028)

You could do something like this with Automation for Jira:

* TRIGGER: **Scheduled (Mark box: Run a JQL search and execute actions)**
  * *status = "Waiting for customer" and updated \< -5d*
* ACTION: Transition issue
  * Done status
* Additionally, you can add a comment to inform the customer

Hope this helps

Best regards

Sam

comments: author: P?tur Bj?rn
body: Thank you [@Samuel Gatica](/t5/user/viewprofilepage/user-id/753028)   
That did the trick


author: Tansu Akdeniz
body: Hi [@P?tur Bj?rn](/t5/user/viewprofilepage/user-id/3659028)

It is possible to define SLA metric for closure time. Then, in automation, when SLA breached, transition issue to closed.

Alternatively, you can use Scheduled trigger and provide a JQL which finds issues waiting then x amount of time without an update, then again change the status to closed via Automation.
How is automation usage really counted?
Asked by Jennifer Pike:

I have an automation that updates multiple fields (say, 10 for the maths) whenever an issue is updated. It also transitions the issue to a new status if that status changed.

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

<https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/> This says that "usage is measured by the number of rules that execute each month". Then it goes on to say "Any time an event fires as a result of an automation rule you have enabled, it will count as a rule execution."

So if a single issue is changed and triggers the automation, is the usage:  
1 because it was one rule triggered  
11 because it checked/ updated 10 fields and the status transition?

Would it be better to have the trigger be a set time during the day and update all issues in one batch?


Answers:
author: Hana Ku?erov?
body: Hi [@Jennifer Pike](/t5/user/viewprofilepage/user-id/1960852) ,

there can be multiple actions in one rule and it will still be 1. If the changes affect only one project, it is 0 actually.

comments: author: Hana Ku?erov?
body: *Would it be better to have the trigger be a set time during the day and update all issues in one batch?*

No. Usage count will be the same and usually it is better to react immediately.


author: Jennifer Pike
body: Why is it better for it to be immediate?
How to use a variable value as an object reference?
Asked by Chad Jackson:

Hello All,

I feel like this should be simpler than it has been and truly do appreciate any and all assistance.

I am using "lookupObjects" to search Assests in (Atlassian Cloud)

Using objectTypeId = "ID" Attributes are Name, Manager, Members

logging {{lookupObject.Name}} returns all 50 Team Names

Manager and Members are Object Links to another objectType where we store user info like name and e-mail. I have a variable created that's being pulled from a (CF) at Issue creation {{TeamName}} Which is populated with a singular assigned team.

The issue I am having is with reference "Name" = {{TeamName}} returning a singular value for {{lookupObjects}} in which I will pull user email address from. Having tried several iteration of putting it all together has left me chasing my tail.

Currently I have everything working if I point at a singular Key = "Key Value" of a team name.

The whole process is to auto assign a new issue to a select team by application value and then e-mail all team members of a new assignment including the issue link and issue information.

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


Answers:
author: Chad Jackson
body: Found the Issue my variable had a typo my lookupObjects searech string looks like this and is working after fixing the typo.

objectTypeId = 29 AND Name = "{{TeamName}}"