youngmon/atlassian-qna huggingface dataset:
Forms - field validation
Asked by Myles Boyd:

Designing a form, where, due to it's criticality and being free text, we have asked the user to type an input twice

Ignoring the fact they can just copy n paste from one to the other, I was trying to find a way to compare the 2 fields and error if not the same

I have set up automation, based on create issue, but was hoping there would be a way to block submit until they match.

Have looked at workflow transition validators, but can't see a way to compare fields.

Any suggestions/ideas appreciated


Answers:
author: Sergio Garc?a-Consuegra _Decadis AG_
body: Hi [@Myles Boyd](/t5/user/viewprofilepage/user-id/4266693) ,

My name is Sergio and I'm a member of the support team from Decadis.  

As Marc already mentioned, this should be able to be done using Jira Workflow Toolbox for Jira Cloud.

You could use the validator suggested or also our validator **[Jira expression validator](https://apps.decadis.net/display/JWTCLOUD/Jira+expression+validator)**, were you should be able to compare both fields with an expression like the following one:

```
issue?.customfield_AAAAA== issue?.customfield_AAAA
```

You should replace AAAAA and BBBBB for the custom field codes you want to compare.

If you have any doubt related to our app, please feel free to contact us through our **[customer portal](https://decadis-apps.atlassian.net/servicedesk/customer/portals)**! We will gladly assist you with any doubt you have :)

Best regards,  
Sergio


author: Marc - Devoteam
body: Hi [@Myles Boyd](/t5/user/viewprofilepage/user-id/4266693)

This could be done by the app Jira Workflow Toolbox.

They have a compare validator, see; <https://apps.decadis.net/display/JWTCLOUD/Compare+two+values+validator#expand-Comparisonvalue>

Your text fields in the form, will have to be linked to Jira custom fields. You can use from fields only.

Give it a try, I can't promise it will work.


Tags: cloud

jira-service-management

jira-service-management-cloud
JQL query
Asked by Ayush Lawania:

How to create a JQL to show the tickets resolved within the 4hours, 8 hours, 12 hours and 16hours from the time of creation.


Answers:
author: Mohaddis Hassan
body: Dear [@Ayush Lawania](/t5/user/viewprofilepage/user-id/5381132) You will get the desired result by changing the hours value.![](https://i.imgur.com/LfHIQir.png)

comments: author: Ayush Lawania
body: hey, it does not work, what i see with this jql is it shows all the issues created within last 4h, but what I am looking for is any issue which was created in any time frame but resolved within those time frames.

[@Mohaddis Hassan](/t5/user/viewprofilepage/user-id/5564723)


author: Mohaddis Hassan
body: Hi,   

Yes, you are right the query will return all the tickets and there is no such query from which we can retrieve this except we can retrieve via automation rule attachment is attached below.  
![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/347261i114EEB56E77BAC04/image-size/large?v=v2&px=999 "image.png")   

<br />


Tags: cloud

jira-service-management

jira-service-management-cloud
Unable to Change Issue Type in Bulk (Jira) - Incompatible Field Configurations and Workflow Associat
Asked by Juan Vicente Rodriguez Rodriguez:

Hi everyone,

I'm currently trying to perform a bulk change in Jira to modify the issue type of 18 issues from "Evolution" to "Bug". However, I'm encountering the following message:

*"Some issue types are unavailable due to incompatible field configuration and/or workflow associations."*

I've checked the project configuration, and both "Evolution" and "Bug" issue types are included in the same field configuration scheme. However, they have different workflows and screen configurations. One thing I noticed is that the **Issue Type** field is not visible on any of the screens (Create, Edit, or View) for these issue types.

Could the missing **Issue Type** field on the screens be the reason I cannot change the issue type? How can I resolve this to successfully change the issue types in bulk? Any guidance on how to fix this issue would be greatly appreciated!

Thanks in advance!


Answers:
author: Jack Brickey
body: Hi [@Juan Vicente Rodriguez Rodriguez](/t5/user/viewprofilepage/user-id/5590753) ,

if the issue types use the same workflow you can use option 1 below, if the option is not allowed you need to use option 2 (Move) so that you can make the necessary decisions, e.g. status mapping, to achieve the change. Option 1 supports bulk edit but option 2 does not.

option 1

![IMG_4578.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/347016i34B420C227C3072D/image-size/large?v=v2&px=999 "IMG_4578.jpeg")

option 2

![IMG_4579.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/347019iA253A66AED1B77C2/image-size/large?v=v2&px=999 "IMG_4579.jpeg")


author: John Funk
body: Hi Juan Vincente,

When you do the Bulk Change, use the Move function instead of the Edit function.


author: Manoj Gangwar
body: Hi [@Juan Vicente Rodriguez Rodriguez](/t5/user/viewprofilepage/user-id/5590753)

Welcome to the Community!

Please refer to the below thread-

<https://community.atlassian.com/t5/Jira-questions/Some-issue-types-are-unavailable-due-to-incompatible-field/qaq-p/326167>


Tags: cloud

jira-service-management

jira-service-management-cloud
request type is not assigned when a ticket comes from the portal
Asked by elizavetaa:

Request type is not assigned when a ticket is received from the Portal. Request Type is associated with the corresponding task type and is configured in the request form on the Portal. What can this problem be related to?


Answers:
author: Jack Brickey
body: Hi [@elizavetaa](/t5/user/viewprofilepage/user-id/5590700) , welcome to the community.

I have never seen this to be the case. Are you observing this yourself and if so are you able to reproduce? Generally the scenario where I see this is when an agent or someone with access to the application, uses the create button within the application and has not set the request type.


Tags: cloud

jira-service-management

jira-service-management-cloud
Project Board setting default View Settings so Quick Filters always display
Asked by Martyn Hughes-Dowdle:

When viewing a project board, the default view setting for quick filters is that they are hidden. I appreciate that they can be displayed for the current window by going into View Settings and enabling Quick Filters, but this setting is forgotten if you navigate away from the page and return to it. Is there a way to ensure that display of quick filter buttons on the board remains by default? Thank you.


Answers:
author: Trudy Claspill
body: Hello [@Martyn Hughes-Dowdle](/t5/user/viewprofilepage/user-id/5527682)

Based on my experimentation the setting of the quick filters and the use of the "show quick filters" toggle is retained, but it is per user and per board.

There does not appear to be any option for setting the Quick Filters option and "locking" that setting for an individual board, nor for all boards for a user.

comments: author: Martyn Hughes-Dowdle
body: Hi Trudy. Thanks for your reply. in my case unfortunately, the setting are not even retained on a per user basis.


Tags: cloud

jira-service-management

jira-service-management-cloud
Exclude weekends from Automation Rule logic
Asked by Nibal Alrabadi:

Hello. So we have a rule in which tickets get auto-resolved if the customer did not reply to our question within 48 hours of asking.

The logic is as such:

- Customer raises a ticket

- Support Agents need more information so they reply to the customer, and change the status of the ticket to "Waiting for Customer"

- If the customer does not reply within 2 working days of changing the status to "Waiting for Customer" the ticket gets automatically resolved.

Wo the rule JQL was set to:  
status = "Waiting for customer" AND updatedDate \<= -48h

Cron expression was:

0 0 9-17 ? \* MON,TUE,WED,THU,FRI \*

Status Equal: Waiting for Customer

Then: Transition issue: "Resolved"

the problem is that this rule does not exclude weekends even with the above defined cron expression. We come on Monday morning to find out that tickets that had status changed on Friday morning already closed.

Knowing that our working hours are 09:00 - 17:00 Monday to Friday is there anything we can do to avoid getting the tickets resolved over the weekend?

For example tickets that we change their status to "Waiting for Customer" on Friday at 16:00 should remain at the same status until Tuesday 16:00 before it gets automatically resolved (2 full calendar working days)

Appreciate your help


Answers:
author: Hans Polder
body: Hi [@Nibal Alrabadi](/t5/user/viewprofilepage/user-id/5486193) ,

Welcome to the community!

You could check out this thread for some inspiration: <https://community.atlassian.com/t5/Jira-questions/Using-business-days-instead-of-calendar-days-in-JQL-query-for/qaq-p/2479986>

If you want more customization on more variable business days, you could also consider adding an SLA to your project that you can configure as you please (when it comes to business hours), and then use [JQL functions for SLA](https://support.atlassian.com/jira-service-management-cloud/docs/write-jql-queries-for-slas/) like **breached()** to identify tickets that are breaching said 'SLA'.

If you need more help, please paste screenshots of your full automation rule, including all configuration of the individual steps, to help us help you better :)


Tags: cloud

jira-service-management

jira-service-management-cloud
Lookup Table - how to iterate through all elements with a For Each Loop
Asked by Wojciech Wardaszko _HeroCoders_:

Hi Community!

Today I've had an interesting challenge which I failed to solve.

A customer wanted to send Slack messages to people who did not track the expected amount of time on the day before. I managed to create a simple automation rule using Clockwork API and a schedule to do that for one user, but we wanted to scale this without creating a separate rule for every user.

Now I've never used Lookup Tables before, but I figured I'd try.  
The setup was this: Jira Account ID was provided as the Key and Slack MemberID was provided as the Value. We could introduce all users manually to the rule this way.

The lookup table was called {{theUsers}}

Then came the Loop: For Each of {{theUsers}} as {{theUser}}, do stuff (send a web request with the account ID as a request parameter, then if conditions met send a Slack message with the MemberID of the same user to ping them in a shared channel. I tried referring to the MemberID with {{theUser.value}}.

This didn't work. The rule kept running without a result for minutes to come.

I understand that lookup tables are designed to work with the .get() function, but I don't want to call any specific account ID. I want to go through all of them one by one. Is this even possible?

[@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)I know you have experience with this stuff, can you help?

Thank you!


Answers:
author: Bill Sheboy
body: Hi [@Wojciech Wardaszko _HeroCoders_](/t5/user/viewprofilepage/user-id/4928380)

In this updated article about lookup tables: <https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798>

It shows the **entries** function to return the rows as a list. Your advanced branch could use:

* smart value: {{theUsers.entries}}
* name: varUser

And the references inside of the branch would be:

{{varUser.key}} and {{varUser.value}}

Kind regards,  
Bill


Tags: lookup-table
Unable to add labels to Automations
Asked by Patrick Ricciardi:

I was able to add Labels to automations in the past. But, I don't seem to be able to do it anymore.

In the [instructions](https://support.atlassian.com/cloud-automation/docs/organize-your-rules-with-labels/#Label-a-rule) it indicates that the "Add Label" button will appear on the side, beneath the different Automation scopes. But, in my Jira instance there is no space on the side with those options. When I go to Automations from Project Settings. There's a dropdown that allows you to choose scope and a dropdown that allows you to edit labels, but no place on the left to Add Labels.

I assume this has been moved recently, but I can't find where. Anyone have any idea?

Thanks.


Answers:
author: Michel Neeser
body: Hi [@Patrick Ricciardi](/t5/user/viewprofilepage/user-id/770651)

The "Add labels" option appears if you hover over the automation rule's "Labels" column on the automations overview page:

![Screenshot 2024-04-23 at 16.12.00.png](https://community.atlassian.com/t5/image/serverpage/image-id/320063iDF5CC9453DAFBF0F/image-size/large?v=v2&px=999 "Screenshot 2024-04-23 at 16.12.00.png")

Let me know if this helps!

comments: author: Patrick Ricciardi
body: Thanks! That's not super intuitive, so this is a time where I don't blame myself for missing it!


Tags: cloud
Automation that will count numbers in the fields (and more)
Asked by Artur:

Hello everyone!  

We would like to create automation that will make some math operations when it comes to filled fields.   
So, just a little background - we already have existing fields, and we don't want to change them/edit as this could impact all the existing tickets. Therefore, we would like to add a new field that will do all the counting.

So:

1. The reporter is required to add a specific digit number in the field "How many months should this apply for";

2. There is a new field - let's name it "How many days?"

3. We would like to transition months from "How many months should this apply for" to days and add it to the new field from point 2;  

4. Furthermore, we would like to add days when the ticket was closed (transitioned to completed status);

5. Automation should work on a daily basis, checking all the existing tickets and do the above;

<br />

For example:  
Ticket was closed on 22/03/2024 (this mean it's 30 days);

This should apply for 6 months (180 days);

Therefore, I would like this field to show 180 days + 30 days = 210 days.  

So far, I manged to figure out how to transition monthly fields to days by using the following:   
{{#=}}{{issue.customfield_x}}\*30{{/}}   
but I have yet to figure out how to combine those with when the ticket was closed.  

Could you please assist?

<br />

Thank you!


Answers:
author: Kalyan Sattaluri
body: Hello [@Artur](/t5/user/viewprofilepage/user-id/5346511)

To calculate how many days ago an issue was closed, you can use: {{issue.resolved.diff(now).days}}

To add this to your existing count, you will use:

{{#=}}{{issue.customfield_x}}\*30 + {{issue.resolved.diff(now).days}}{{/}}

And why not set up a trigger = issue transitioned to "Done or whichever statuses" and then update your new field with above smart value?

comments: author: Artur
body: Hey [@Kalyan Sattaluri](/t5/user/viewprofilepage/user-id/5312306) ,

Thank you so much!

Yes, we may consider this in the future, but for now we need to identify and update older tickets.  

I tried your suggestion and unfortunately, I got an error:

"Error rendering smart-values when executing this rule:

Missing parameter(s) for operatora +:10.0\*30+ "


author: Kalyan Sattaluri
body: Please share a screenshot of your rule and copy paste your syntax as well.
Sum of custom numeric field from different EPICS
Asked by Shah Hussain:

Hello Community,  

I have a custom numeric field - "Effort savings", each EPIC has a value in it. Let say, I have 10 EPICS, so, I want to sum the values of "Effort savings" field from 10 EPICS and show in a gadget as a total effort savings in Dashboard. Any idea how I can achieve this?


Answers:
author: Marlene Kegel - codefortynine
body: Welcome to the community, [@Shah Hussain](/t5/user/viewprofilepage/user-id/5481215).

I am Marlene, product manager of [Quick Filters for Jira Dashboards.](https://marketplace.atlassian.com/apps/1220136?utm_source=atlassian&utm_medium=referral&utm_campaign=quickj-new-reach-com-2678107)

With our app you can [sum up any Jira number field,](https://documentation.codefortynine.com/quick-filters-for-jira-dashboards/aggregate-values-of-jira-number-fields?utm_source=atlassian&utm_medium=referral&utm_campaign=quickj-new-reach-com-2678107) including custom fields. This feature is supported for the Quick Two Dimensional Filter Statistics gadget, the Quick Issue Statistics gadget and the Quick Pie Chart gadget.

You can [check out our app without installation on our demo dashboards.](https://codefortynine-demo.atlassian.net/jira/dashboards/10003?utm_source=atlassian&utm_medium=referral&utm_campaign=quickj-new-reach-com-2678107)

![quick-filters-jira-dashboards_sum-up-custom-number-fields.png](https://community.atlassian.com/t5/image/serverpage/image-id/321576iC36297F2ADD449A4/image-size/large?v=v2&px=999 "quick-filters-jira-dashboards_sum-up-custom-number-fields.png")

comments: author: Shah Hussain
body: Hi [@Marlene Kegel - codefortynine](/t5/user/viewprofilepage/user-id/2498951)  

Thanks for the response. However, I am unable to find the gadgets you have shared. Any idea what could be the reason? or am I missing something?  

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


author: Marlene Kegel - codefortynine
body: [Quick Filters for Jira Dashboards](https://marketplace.atlassian.com/apps/1220136?utm_source=atlassian&utm_medium=referral&utm_campaign=quickj-new-reach-com-2678107) is a Atlassian Marketplace App and needs to be installed to your instance.

Here's an instruction about how to install apps to your instance: <https://documentation.codefortynine.com/quick-filters-for-jira-dashboards/installation>


Tags: calculation

custom-field

dashboard

epic

gadget

jira

numeric

sum
Atlassian Intelligence
Asked by Akshay Tiwari:

Actually I want to use Atlassian Intelligence for creating my own Automation rule for my organisation, Please let me know How I can access that


Answers:
author: Nikola Perisic
body: Welcome to the community [@Akshay Tiwari](/t5/user/viewprofilepage/user-id/5478925)

First, make sure that Atlassian Intelligence is enabled on your site. You need to go to admin.atlassian.com, choose your organisation, go to Atlassian Intelligence and enable it from there.

Some of the users will see the automation, some not, since they have applied for the closed beta of Atlassian Intelligence for Automation rules. If you don't have the window that is prompting you to write your own automation, this means that you don't have the access yet.

comments: author: Akshay Tiwari
body: firstly of all, thanks for clarifying and secondly how i can get that access if you let me know


author: Nikola Perisic
body: Not even I have the access to this feature yet. The enterprise users usually get the access to this feature first. There is no link for the access program. Official documentation is here: <https://support.atlassian.com/cloud-automation/docs/use-atlassian-intelligence-with-jira-automation/#How-do-I-use-Atlassian-Intelligence-to-create-a-rule>


author: Akshay Tiwari
body: okay
Run rule once for multiple trigger
Asked by jprieto:

I am monitoring Jira items to trigger my rule when one of four field values are changed. However, I'd like to only run the rule once if all four values change, not four times. Is this possible?


Answers:
author: Bill Sheboy
body: Hi [@jprieto](/t5/user/viewprofilepage/user-id/3668007)

Short answer: no, however...

What actions does your rule do *when one of four fields are changed*?

If this is a one-time action, the rule could be triggered on a change to any of the four fields, and then immediately after the trigger use a condition to check if the action happened yet. If not, proceed with processing.

Kind regards,  
Bill


author: Vijay Dadi
body: [@jprieto](/t5/user/viewprofilepage/user-id/3668007) I guess you can do it,

When the rule is executed for the first time, have one flag on the issue and set it to True/Yes.

And add that field in your If condition.

Hope this helps !

Regards,

Vijay


author: Kalyan Sattaluri
body: What do you mean all four values change?

You could in theory do a lot of if conditions to check specific combination of values in these 4 fields and only continue forward if needed...

But if I have to guess your requirement, (which is lengthy to explain my i am guessing either these combinations will be a lot or includes free text field or you want it extensible) .. my immediate answer is No.

My suggestion instead is for you to do rethink your physical process and workflow so you dont need such a trigger.


Tags: trigger
[JWM & JSW] set a value in the Parent field after issue creation
Asked by Kate Pawlak _Appsvio_:

I would like to create an automation rule which is triggered by Issue created. When some conditions are met, I would like to set the issue key in the Parent field. The issue key is always the same, for example HRA-36.

Do you know how to do it?

I was trying with Edit issues but no actions were performed.

![Rule_builder_-_Automation_-_Human_Resources_Appsvio_-_Jira.png](https://community.atlassian.com/t5/image/serverpage/image-id/319215i4C767D81729F507C/image-size/large?v=v2&px=999 "Rule_builder_-_Automation_-_Human_Resources_Appsvio_-_Jira.png")


Answers:
author: Kate Pawlak _Appsvio_
body: **UPDATE:**

Thanks to [@Luis Machado](/t5/user/viewprofilepage/user-id/5470339), the automation rule works. You have to change "set" to "key" and remove curly brackets. So this is the correct syntax:

```
{
"fields": {
"parent": {
"key": "HRA-36"
}
}
}
```


Tags: cloud

jira-software

jira-work-management
Doesn't count correctly
Asked by koutarou ishibashi:

There are 11 stories under one Epic  
Epic has a field "counter"

In JIRA automation, when the status of the story triggers a change, the parent epic's counter is +1  
{{#=}} {{issue.customfield_xxxxx\|0}} + 1{{/}}

If you change the status of 11 stories at once,  
The Epic counter should be 11, but it could be 6 or 7.?Why??Isn't JIRA exclusively controlled?


Answers:
author: John Funk
body: Hi Koutarou,

How are you changing all 11 at once?

Also, can you share the rule and the audit log that fires when you change all 11 at once?

comments: author: Bill Sheboy
body: Hi [@koutarou ishibashi](/t5/user/viewprofilepage/user-id/5308713)

Yes, and...to John's suggestions:

When summing / counting issues in a parent for child issues, I recommend completely recalculating the value spanning the child issues rather than just doing an increment / decrement. That will ensure there are fewer errors due to timing / rule engine problems in rule processing.

Also, please describe *how you are changing the status* of 11 stories at once: manually, bulk update, with the REST API functions, with an automation rule, etc. Knowing that may help explain this symptom.

Kind regards,  
Bill