youngmon/atlassian-qna huggingface dataset:
Rate Limited
Asked by Robert Ogden:

We have an Exchange email account that we utilize for user to email in requests for the past month or so we have been seeing a boat load of Rate Limited failure in the connectivity logs and people complaining they are able to create a ticket. If we utilize the [@atlassian](/t5/user/viewprofilepage/user-id/62094).net email address we do not have any problems. I have begun looking into this but wanted to see if anyone else came across the issue. I have submtted a ticket to support.![Screenshot 2024-06-25 132206.png](/t5/image/serverpage/image-id/331709iF5C0DA1E52C0F967/image-size/large?v=v2&px=999 "Screenshot 2024-06-25 132206.png")


Answers:
author: Joseph Chung Yin
body: [@Robert Ogden](/t5/user/viewprofilepage/user-id/5363367) -

Typically the problem is at the receiving end. I would recommend you to work with your Exchange team to determine the root cause. I don't believe it is a problem on the Atlassian side.

Hope this helps.

Best, Joseph

comments: author: Robert Ogden
body: Joseph

You are correct we simply removed the old email address and added it back in and everything worked perfectly, the only thing is we have a 30 emails in the Outlook inbox that need to get forwarded for ticket creation. There was a policy change done about a day before everything started failing.

Thanks

Rob


Tags: cloud

jira-service-management

jira-service-management-cloud
How do you install the Asset management agent using Intune
Asked by Jim Hartmann:

Looking to use Intune to push out the asset management discovery agent. Is there any details available for this process? And any help on any configurations that are needed would be a big plus. Thanks in Advance


Answers:
author: Fabian Lim
body: Hi [@Jim Hartmann](/t5/user/viewprofilepage/user-id/5528943)

I suggest you look into the marketplace or wait until end of September where this will be ouf of the box when they introduce the asset manager (aka airtrack).

I have integrated Intune with the PIO vendor (<https://marketplace.atlassian.com/apps/1230667/microsoft-intune-importer-for-jsm-assets?tab=overview>) and it has worked great.

Regards,

Fabian


Tags: asset-management

cloud

jira-service-management

jira-service-management-cloud
Jira custom fields date in subtask
Asked by Michael Pierotti:

Why would my data in a issue / task not carry to a sub task. I.E. I have a custom field VENDOR CONSTRUCTION COMPANY in my tasks which is populated but in my sub task it is empty


Answers:
author: YY Brother
body: Hi [@Michael Pierotti](/t5/user/viewprofilepage/user-id/5513875)

Welcome to our Community.

This field value is not inherited from Task to its Sub-tasks in Jira.

The common solution is to use Jira automation to copy that value to sub-tasks.

Thanks,

YY?


Tags: cloud

jira-service-management

jira-service-management-cloud
Opsgenie is firing unwanted alerts to JSM
Asked by Kay:

Opsgenie was configured to fire alerts to JSM and JSM automation create incidents from those alerts but alerts from other departments that uses opsgenie is also being fired to JSM and incidents are being created which I do not want.

I edited the JSM automation to only create incidents from alerts using issue field conditions such as the summary and description from the alerts (the naming convention for the wanted alerts is different from that of the unwanted ones) yet incidents are still being created from the unwanted alerts.

How do I fix this?


Answers:
author: Melo
body: Hi [@Kay](/t5/user/viewprofilepage/user-id/5428035),

It's been a while since I used Opsgenie, but I used to create issues/incidents in JSM via an integration configured on the Opsgenie side. Have you checked those settings? You might need to adjust the filter or scope there.

Hope this helps.

Cheers,  

Melo


Tags: cloud

jira-service-management

jira-service-management-cloud

opsgenie
Based on App Name field value assign value to plugin group and assignee using script runner
Asked by ananda_kumar_b_h:

We have multiple applications based on application field value we need to assign the ticket automatically to Group (Plugin Field - plugin Group assignee).

please help me with script runner script to do this


Answers:
author: Gaurav
body: Hello [@ananda_kumar_b_h](/t5/user/viewprofilepage/user-id/5528827)

Welcome to the community!!

This can also be achieved using Automation, within Jira Service Management.

The automation rules have 3 parts, Trigger, Condition and Action.

For this case, the Trigger would be ticket creation; the Condition would be the Application Name and the Action would be setting the Assignee.

Here, we can even have multiple application names in the same condition.

Kindly let me know if this helps or if further support is required.

--GG


Tags: jira-service-desk-data-center

jira-service-management

jira-service-management-data-center
One Dashboard to rule them all
Asked by Conrad Randall:

Hi, can I create one dashboard for many projects? What permissions do I need for that?


Answers:
author: Marlene Kegel - codefortynine
body: Welcome to the community, [@Conrad Randall](/t5/user/viewprofilepage/user-id/5528589)!

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-2735976)

As [@Sam Bartolome](/t5/user/viewprofilepage/user-id/5515349) mentioned, that is the awesome part about Jira dashboards, that you can create them across projects and view results from different projects on one dashboard.

For every gadget you can select custom filters, which can be created under "filters" \> "view all issues". You do not need a Marketplace app for this.

If you want to have more flexibility in what you show on your cross-project dashboard, you can check out our app Quick Filters for Jira Dashboards. Our Jira cloud app provides a Quick Controller gadget that enables you to dynamically filter you dashboard.

With the Quick Controller you could e.g. filter per project, if you want to view only the results for one project. But also other filters are possible, like priority, sprints, epics, ...

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

![quick-filters-jira-dashboards_controller_pie-chart_epic-link.png](https://community.atlassian.com/t5/image/serverpage/image-id/334521i6040D713C70E11C6/image-size/large?v=v2&px=999 "quick-filters-jira-dashboards_controller_pie-chart_epic-link.png")


author: Sam Bartolome
body: Hi [@Conrad Randall](/t5/user/viewprofilepage/user-id/5528589)

Welcome to the Atlassian Community!!

You can create a dashboard for many projects indeed.

Be aware that in order for users to see the same content, they all should have the same level of permissions otherwise results may vary although you may need to restrict access based on your requirements.

You can set the permission that would allow users to access Jira (jira-software-users or similar), but consider if the instance is for internal use or also with partners which may not need such dashboard.

Sam


Tags: cloud

dashboard

jira-service-management

jira-service-management-cloud
Where can I edit the dropdown lists appearing in Help Center => Requests?
Asked by Daniel Reske:

Dear Community,

I'd like to limit the choice for Customers down to specific values appearing in dropdown lists / filters you can use in Help Center =\> Requests:

![Screenshot 2024-06-25 153652.png](/t5/image/serverpage/image-id/331653iA91884B647D50F66/image-size/large?v=v2&px=999 "Screenshot 2024-06-25 153652.png")

The question is: where can I tick off the values in "Status" and "Request Type" to limit Customers' choice from the following 5 fields:

![Screenshot 2024-06-25 154147.png](/t5/image/serverpage/image-id/331656iF8A0534465251A96/image-size/large?v=v2&px=999 "Screenshot 2024-06-25 154147.png")

..down to the ticked 3 fields?:

![Screenshot 2024-06-25 154320.png](/t5/image/serverpage/image-id/331657i03991FA23070F6E4/image-size/large?v=v2&px=999 "Screenshot 2024-06-25 154320.png")

In other words: In Help Center I'd like to hide from Customers the fields "Investigate a problem" and "Create a post-incident review".

Is there any possibility to do that?

Thank you in advance for your reply


Answers:
author: Sam Bartolome
body: Hi [@Daniel Reske](/t5/user/viewprofilepage/user-id/5514656)

You can remove the Request Types from the portal on Project Settings\>Request Types. On the left-pane select the work categories, Problems and Post-incident reviews. Select the 3-dot on each item and then select the Edit option (from Portal Group).

Note, this is for the Portal Group. Your screenshots are represented from the user own request view which is different.

To make it fully disappear you could remove the non-wanted options and if any issue is already in those types, migrate them.  

Earlier today, Atlassian made public restrictions on request types which may help you too,

<https://community.atlassian.com/t5/Jira-Service-Management-articles/Announcing-request-type-restrictions-in-Jira-Service-Management/ba-p/2735416#M4670>

Sam


Tags: cloud

jira-service-management

jira-service-management-cloud
Email Issue Watchers in Automation
Asked by Mark Wheeler:

Is there a way to email the users who are watching an issue when sending an email via Jira Automation?

I can send to the Reporter, Assignee or user fields on the issue but can't see an option for the Watchers of an issue.

This would be really useful functionality.


Answers:
author: Kirkie
body: You should be able to add this in the email TO section:

`{{issue.watchers.emailAddress}}`

More information on smart values can be found here:

<https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/?_ga=2.124031948.793959474.1597669004-962904791.1585928062>

comments: author: Mark Wheeler
body: Brilliant - thanks.

Didn't realise I could put Smart Values in the email to and cc boxes.

Mark


author: Mariana_Pryshliak_Saasjet
body: Hello [@Mark Wheeler](/t5/user/viewprofilepage/user-id/3163878)

In this discussion you can find a solution for your issue:

<https://community.atlassian.com/t5/Jira-questions/Issue-watchers-not-receiving-email-notifications/qaq-p/326154>

I hope it helps.


Tags: watcher
Translate user IDs in comments within Jira Automation messaging
Asked by Mark Wheeler:

Is it possible to translate User IDs referred to in Comments when displaying a comment as part of a Jira Automation action?

I send an email as part of a Jira Automation and include the below:

Latest comment:  
{{issue.comments.last.body}}

But this produces something like the below:

\[\~accountid:5c9a182a03b8be71089b443f\] I've checked with \[\~accountid:5d7b887d656e2a0dbab30627\] and he recommended this action  

cc \[\~accountid:5be4242c8298307a1e93bf00\] \[\~accountid:5a952edb74e8e143a0ac6e88\]

I'd like to translate the IDs into the user display names. Any idea as to how to do this if this is possible?


Answers:
author: Yvan Martin
body: Hi there Mark,  

Developer from Automation here,  

There are some limitations in what we display from that comment, it's basically what the API gives us. Although usually it does give the displayName, if you specify the body text/html in that smart value. Also since you are sending an email than it's also worth including the html tag to preserve links from the comment wiki markup.  

Try either {{issue.comments.last.body.html}} for that html generated output, or {{issue.comments.last.body.text}}  

I hope this helps.


author: Kirkie
body: [@Mark Wheeler](/t5/user/viewprofilepage/user-id/3163878)

This is a known issue for Cloud.

Here is the announced changes to usernames in Cloud:

<https://confluence.atlassian.com/jirasoftwarecloud/gdpr-changes-to-usernames-in-jira-cloud-967319102.html>

Followed by the impact of this to how smart values work in Automation:

<https://support.atlassian.com/jira-software-cloud/docs/convert-usernames-to-user-account-i-ds/>

While you can see there are ways to convert the id to display name, they do not provide a way to parse through the comment and convert portions of the string.

I would submit a Bug or Support ticket with Atlassian to see if there is a workaround or if they can hopefully add this functionality because I am sure it will be useful for users moving forward.

comments: author: Mark Wheeler
body: I was aware of the data protection reason for the IDs, but is annoying.

Thanks for the suggestion and I'll raise a ticket with Atlassian.
Automation
Asked by Peter Knaus:

I'd like to set up an automation for the following example:

If an issue type is created i want it automaticly to be set up with the priority "medium" (thats no problem and worked out well)

Then i want there to be an automation that raises the priority to high after x weeks if nobody worked on it ( updated it) and automaticly raise to the highest after following x weeks.

I tried it with a scheduled trigger:

updated \<= "-Xw" and priority = medium and status != DONE + a cron to run daily.

Didn't seem to work...


Answers:
author: Rudy Holtkamp
body: Hi [@Peter Knaus](/t5/user/viewprofilepage/user-id/4023092) ,

This should work (if X=3):

```
priority = medium and updated <= -3w and resolution is empty
```

So you might want to remove the quotes around -Xw.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/107029i56499F6042C2BBFA/image-size/large?v=v2&px=999 "image.png")Also use 'Validate query' to check if your JQL returns something. Then use 5 minutes to trigger to see if things work, if so change it back to daily triggering.

**Tip**: If you use post-functions to set the resolution when an issue is done/rejected/duplicate then it is best-practice to use resolution in your JQL.

comments: author: Peter Knaus
body: Thanks!
Updating Epic Link via automation
Asked by Sean Wiese:

I am new to Jira Automation, and working on a scenario where on a transition, I am creating linked tickets. The original ticket is part of an epic, and I would like that epic to also be on the newly created tickets.

Happy to provide additional details.

screenshot is the relevant portion I am stuck on.

![Screen Shot 2020-08-17 at 5.36.01 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/106968i673F0BEC80CB7CFE/image-size/large?v=v2&px=999 "Screen Shot 2020-08-17 at 5.36.01 PM.png")


Answers:
author: Mark Chaimungkalanont
body: Hey there Sean,

You should be able to set the Original estimate and the Epic Link in the Create issue action itself without need the extra Edit actions. You need to set the value of the Epic Link to the "Trigger issue"

If editing the Epic Link isn't working, are you using a NextGen project? They deal with Epic Links differently to Classic projects

Cheers,

Mark C

comments: author: Sean Wiese
body: Mark - that was def my first choice to set all the things in the create. but I ended up with the edit action since that seemed the only way to get the Orig Est field to work.

added details of the create and the whole trigger.

Not using a next-gen project.

I may just not be groking the "copy from" term, as I dont see that in the epic link options.

also attached.

![Screen Shot 2020-08-18 at 8.38.21 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/107070iF41438B86025879D/image-size/large?v=v2&px=999 "Screen Shot 2020-08-18 at 8.38.21 AM.png")![Screen Shot 2020-08-18 at 8.35.55 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/107071iE65BA0864E7FA679/image-size/large?v=v2&px=999 "Screen Shot 2020-08-18 at 8.35.55 AM.png")![Screen Shot 2020-08-18 at 8.37.39 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/107072i49521177F8FD605B/image-size/large?v=v2&px=999 "Screen Shot 2020-08-18 at 8.37.39 AM.png")


author: Sean Wiese
body: and solved. I guess I just didnt see the field to set as a "copy from" action. seems to be working now, in the create action!


author: Ste Wright
body: Hi [@Sean Wiese](/t5/user/viewprofilepage/user-id/1183003)

Can you provide the full rule?

Mark's method of utilising the "Copy From..." function for setting field values is the ideal option for this issue - but if there is more to the rule it might benefit to see this :)

Ste

comments: author: Sean Wiese
body: thanks! updated via reply on Mark's comment.


author: Marc Isikoff
body: And if we change the scenario slightly to automate creation of an Epic then a Story, how do we establish Epic Link on the story as triggeringIssue is not the Epic nor can we Copy from Epic issue (not established yet) nor Parent Issue (for sub-tasks only)


author: Marc Isikoff
body: Nevermind found it: {{#createdIssues}}{{key}}{{/}}
Auto updating linked issues when an epics fix/version is updated
Asked by Craig Buchanan:

I want to update the fix/version linked to my epic whenever the epic's fix/version is updated.

To complicate matters my epic and linked issues are in different projects.

I have tried creating a rule in the epic project that triggered based on an update to the fix/version but I can't get it to update the issues. Whenever the rule runs it is recording a successful run at the epic level i.e. tagging it with the same version that I just updated it to

P.s. I am using automation for jira


Answers:
author: Ste Wright
body: Hi [@Craig Buchanan](/t5/user/viewprofilepage/user-id/4052131)

Just to confirm:

* You want to update the FixVersion for issues which are children of your Epic
* This should happen either when the FixVersion is changed in your Epic or...
* A new issue is moved into the Epic
* The Epic and the children are in different projects

\^ The last bullet point is a difficult issue - Versions are project-specific, so if the Epic is in one project and the issues in another - are these two separate Versions with the same name? Or does one Epic project version relate to a specific child-level version?

Also to run a rule where issues from another project are actioned, it'll need to be a global rule.

Let us know if the above is accurate, and I'll try to help provide a good rule option :)

Ste

comments: author: Craig Buchanan
body: Hi [@Ste Wright](/t5/user/viewprofilepage/user-id/1166470)

Your understand is correct. The versions are cross project releases setup using Portfolio.

I suspect that my administrator has disabled global rules. So was even wondering if there was an option to do a scheduled rule that checks say on a weekly basis to make sure things remain in sync and setup a separate rule to deal with when an issue is created.

Any help you can give would be really appreciated

Craig


author: Mark Chaimungkalanont
body: Hey there Craig,
> I suspect that my administrator has disabled global rules

You're probably not seeing this option at the moment since only global admins can administer global / cross-project rules <https://codebarrel.atlassian.net/browse/AUT-1261>

There are not too many workarounds at the moment apart from getting your global admin to create this rule for you.

Cheers,

Mark C
Autolinking tickets to a particular issuetype within a fixversion
Asked by Larry Katz:

The question is:  
Is there a way in Automation for JIRA to automatically link tickets that are within a fixversion to a specific ticket type also within that same fixversion?  

I would run this on the scheduler trigger, but the goal is this.  

Fixversion is established: lets call it release-abcd

<br />

I have a current working automation that when a new fixversion is created it creates a ticket of issuetype called "Release Candidate" and added the created fixversion to it.  

If any tickets (bug, task, story) are added to the above fixversion, I ideally want to have something auto link those tickets to the Release Candidate ticket which is also within the same fixversion.  

There would be only 1 RC ticket per release and only 1 RC ticket per fixversion.  

Is this even possible?


Answers:
author: Ste Wright
body: Hi [@Larry Katz](/t5/user/viewprofilepage/user-id/3460959)

To confirm:

* There is one issue per release of type "Release Candidate"
* RC has a FixVersion, unique to it
* If Bugs, Stories or Tasks have the same FixVersion added to it - they should auto-link to the RC issue

------------------

If yes, this is how I got it to work:

1. **Trigger:** Field Value Changed - FixVersions
2. **Condition:** Issue Fields Condition - Issue Type (field) is one of (condition) Story, Task, Bug (value)
3. **Branch:** JQL (type of related issue) - JQL: issuetype = "Release Candidate"
4. **Condition:** Issue Fields Condition - FixVersion (field) equals (in any order) (condition) Fix Versions from the trigger issue (field)
5. **Action:** Link Issues - \<\<link type here\>\> (this issue) trigger issue (issue)

------------------

\^ Remember for the link type in **Step 5** - you are linking from the Release Candidate to the other issue, due to the **Branch** in **Step 3**.

You can modify part of the rule depending on your specific need - for example:

* Modify the condition in **Step 4** to equal all FixVersions in a Release Candidate if there are more than one, or any other condition you prefer
* Add an additional **Condition** before the branch, to ensure FixVersion is not empty on the trigger issue, if there are Release Candidates with no FixVersion

------------------

Let us know if this works for you :)

Ste

comments: author: Larry Katz
body: This is EXACTLY what I needed, and works perfectly, Thanks much! I was looking at the trigger wrong, field value changed for fixversion for sure did it. Much Appreciated.
Access "Development" field contents
Asked by Chris Melville:

I'm looking to determine whether any open PR's exist on an issue. I can get to {{iissue.Development}} but is there an easy way to extract the equivalent of this JQL "Development \[pullrequests\].open \> 0"


Answers:
author: Kevin Bui
body: Hi [@Chris Melville](/t5/user/viewprofilepage/user-id/2952911), could you please provide more information on what you're trying to do?

I'm not sure if this answers your question, but using the **Lookup issues** action you can enter your JQL query, and then have your automation rule perform actions on those issues (e.g.: Comment on each issue where Development \[pullrequests\].open \> 0).

You can learn more about Lookup issues at our [Actions documentation](https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues).

Hope that helps - Please feel free to respond if this doesn't answer your question.

comments: author: Chris Melville
body: Thank you [@Kevin Bui](/t5/user/viewprofilepage/user-id/153300) but I cannot find the "Lookup Issues" action. I am using JIRA server 8.5.1 with the latest version of Automation for Jira. Is this a case of lagging support for server installations or do I just need to upgrade?


author: Chris Melville
body: To actually answer your question... what I want to do is locate any issues with open PR's and transition them back to "in review" status. I have automatic triggers set up to transition on PR merge, but if there are multiple PR's open for an issue I need to either prevent the transition until **all** PR's are merged (best), or look for issues that need to go back to review status as long as there is at least one open PR.