youngmon/atlassian-qna huggingface dataset:
View form in the app
Asked by Rafael Fernandes:

I am unable to view the attached forms via the app (Jira).

<br />

Is there any configuration?


Answers:
author: MobilityStream
body: Hi [@Rafael Fernandes](/t5/user/viewprofilepage/user-id/5325868) ,

You can try out our Jira mobile apps. They currently support the following ProForm functionality:

* JSM Portal - create/edit/view [Android](https://play.google.com/store/apps/details?id=com.mobilitystream.mobilityjsd), [iOS](https://apps.apple.com/us/app/mobility-for-jira-portal/id1418961567)
* Jira - view only (create/edit on roadmap) [Android](https://play.google.com/store/apps/details?id=net.luethi.jiraconnectandroid.jiraconnect), [iOS](https://apps.apple.com/us/app/mobility-for-jira-team/id898500641)

To get started install the [Mobility for Jira add-on](https://marketplace.atlassian.com/apps/1211459/mobility-for-jira-mobile-for-enterprise-teams) from the Atlassian Marketplace.

Kind regards,

The Mobility Team


author: Christopher Yen
body: Hi [@Rafael Fernandes](/t5/user/viewprofilepage/user-id/5325868) welcome to the community!

Unfortunately I don't believe forms is supported in the Jira mobile app at the moment

There is a suggestion for Atlassian to provide support that is currently still gathering interest, make sure to vote for the issue to let Atlassian know this feature is important.

<https://jira.atlassian.com/browse/JSDCLOUD-10674>

from some of the comments it seems like it may be coming soon but it's not functional yet


Tags: cloud

jira-service-management

jira-service-management-cloud
Jira automation Edit Object action to update User attribute to Null
Asked by Tania Schmittou:

When a Team Member exits our company, we desire to remove them from their software licenses setup in Jira Assets as objects. I would like to utilize a Jira automation to accomplish this. A search can return 1-n objects with 1-n Users per object. If there is an object returned with just this Team Member as the sole user, can I use the Edit Object action to remove them? It doesn't seem that I can update that field due to compatibility concerns. I have tried smart values of null and clear. Is the accomplishable?


Answers:
author: Christopher Yen
body: Hi [@Tania Schmittou](/t5/user/viewprofilepage/user-id/2665858)

I'm not sure if this will be the fix but when I was using automation to update my asset objects the edit object action did not work at all for me. There is an action called "Edit asset field attributes" and that ended up working for me. Using that action you can add either a string value, an object id or a smart value in the fields.

![2024-07-30 12_00_21-Rule builder - Automation - Employee Lifecycle - Jira.png](https://community.atlassian.com/t5/image/serverpage/image-id/338955iB9BE558D0FEBA2BF/image-size/large?v=v2&px=999 "2024-07-30 12_00_21-Rule builder - Automation - Employee Lifecycle - Jira.png")

comments: author: Tania Schmittou
body: [@Christopher Yen](/t5/user/viewprofilepage/user-id/5051689) - thank you for the recommendation. It appears the incompatibility error goes away when using the Edit Assets field attributes action and it takes the {{null}} value.


Tags: assets

cloud

jira-service-management

jira-service-management-cloud
Will changing ITSM email address break the link on existing open tickets?
Asked by Ben Larson:

Hi,

I have changed the email address to submit tickets tickets on an ITSM project in the past and it seemed to not allow any updates to the user of progress once changed. I am referring to changing the Project1@company.com to Project2@company.com. Will this break the linkage on the open tickets or there should be no issue?


Answers:
author: Jack Brickey
body: It will not break anything. The only consideration here is that your customers now need to know not to use the old address.


Tags: cloud

jira-service-management

jira-service-management-cloud
How to put email distribution groups in "Assginee field"?
Asked by Muhammad Ali Khan:

We have different teams working in ICT. We assign tickets to the groups, and then the resource who is working on any ticket, assign it him using "Assign to me" option....I need to know to put "Email distribution group" in "Assignee" field in JIRA service management.


Answers:
author: Kai Becker
body: Hi [@Muhammad Ali Khan](/t5/user/viewprofilepage/user-id/5460324)

thanks for the question.

The only solution for this would be the creation of Atlassian Accounts with this distribution groups. This comes with the tradeoff that you will have to pay for these dummy users too.


author: Trudy Claspill
body: Hello [@Muhammad Ali Khan](/t5/user/viewprofilepage/user-id/5460324)

You might want to instead consider using a Group Picker field along with User Groups that you define, or the Atlassian Team feature with the Team field, as a method for "assigning" the issues to a team.

Atlassian Team: <https://support.atlassian.com/atlassian-account/docs/what-is-an-atlassian-team/>

User Groups: <https://support.atlassian.com/jira-cloud-administration/docs/create-and-update-groups/>


Tags: cloud

jira-service-management

jira-service-management-cloud
how setting share request for each external customer of each organization ?
Asked by giorgio rastrelli:

Hi , I hav e two questions:

- it is possible to decide , within an organization, which external clients share their requests from portal and which ones do not?

- Is it possible, within an organization, an external client who sees all the requests from portal of external clients belonging to the organization?

thanks in advance


Answers:
author: Adolfo Casari
body: [@giorgio rastrelli](/t5/user/viewprofilepage/user-id/2489928)A portal user (customer) can choose when creating the ticket to share it within his organization or make it private. If the option is to share, all users from that organization will see the ticket (filter is: created by anyone).

comments: author: giorgio rastrelli
body: Hi Adolfo,

I will attempt to clarify my requirements. I need to configure at the organization level whether the customers of the organization are allowed to share tickets. If I decide that sharing is not permitted, I would like the system to provide an option to enable this setting.

thanks in advance

Giorgio


Tags: cloud

jira-service-management

jira-service-management-cloud
Trigger Automation when Sprint Dates Added
Asked by Ellis Coon:

I'm trying to run a check each time a sprint's start or end date is updated.

The goal is to get issues assigned to the sprint based on a date field of their own.

I have the automation working, but only with a trigger of *Sprint started* as the start/end dates of the sprint are not populated until after it is created.

Any ideas on an alternate trigger to use that would allow me to access *sprint.endDate* and other sprint smart values?


Answers:
author: Bill Sheboy
body: Hi [@Ellis Coon](/t5/user/viewprofilepage/user-id/2791613)

First thing, I am assuming that you are trying to automatically assign issues \*before\* sprint planning, and that during sprint planning the team would make adjustments based on capacity.

On to your question...

There is an open suggestions to add a "sprint updated" trigger, which you may watch/vote for to see progress: <https://jira.atlassian.com/browse/JSWCLOUD-22637>

Until that becomes available, one work-around would be below. Please note I have not tried such a rule to solve this specific problem.

* a rule triggered on an issue change of Due Date, or a scheduled/manual trigger rule
* which calls the REST API using a web request to gather all the future sprints for the board
* find the relevant sprint for the Due Date using list filtering, and
* add the issue to the sprint

Depending upon how this rule is implemented, it could take several seconds to run. For example, if this happens based on an issue Due Date change, that would be several seconds per issue. If instead this ran on a schedule, it may be possible to use just one call to the REST API to update several issues.

Kind regards,  
Bill


author: Jack Brickey
body: Hi [@Ellis Coon](/t5/user/viewprofilepage/user-id/2791613) , those dates are not accessible to query. I don't quite understand your goal. Are you saying you wish to derive what sprint an issue guests assigned to based upon the issue's due date?


Tags: trigger
automation rule to closing the tickets after three contacts with customer or external user.
Asked by Vaishnavi Sharath:

we need automation rule to closing the tickets after three contacts with customer/external user-3 comments in a row ,mentioning reporter/external user without customer responses between our response.

please assist us on creating automation rule for this.


Answers:
author: Dan Tombs
body: Hi [@Vaishnavi Sharath](/t5/user/viewprofilepage/user-id/5004595)

If you are using JSM (Jira Service Management), You can create SLAs. Then on the breach of these (depending on how often you want to use a 'strike'), you can then run an automation to do something. For example, here at intelliflo we have a two strike policy. The first after 3 working days, this will just send an additional comment to the user to chase them. After another two days we auto close the ticket.

These are really easy rules to implement as SLA thresholds are a trigger and commenting, transitioning are easy actions.

Dan


author: Bill Sheboy
body: Hi [@Vaishnavi Sharath](/t5/user/viewprofilepage/user-id/5004595) -- Welcome to the Atlassian Community!

For a threshold counter like this, you may need to implement this yourself using a custom field and an automation rule.

For example, creating a rule triggered on the issue being commented, and...

* if the comment is from a customer, reset the counter to 0,
* else increment the counter, and
* finally then test the counter to learn if it exceeds your threshold to take actions

To get you started on creating your rule, please review this documentation and examples:

* <https://www.atlassian.com/software/jira/guides/expand-jira/automation>
* <https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/>
* [https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all\&page=1\&pageSize=20\&sortKey=name\&sortOrder=ASC](https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC)

Kind regards,  
Bill
New tickets automatically get moved to the current sprint
Asked by Rajesh Shetty:

Hi,  
We use to automatically create Jira tickets from the functional account.

This is functional however we are looking to have new tickets automatically get moved to the current sprint of the XYZ board.

Thanks in advance.

\~Rajesh


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

What problem are you trying to solve by doing this?

As Nic notes, automatically adding work to an in-progress sprint will have unintended consequences...such as reducing your team's confidence/predictability of sprint planning to deliver value.

Kind regards,  
Bill


author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

Doing this destroys the usefulness of Scrum, so it is a really terrible idea. It's the antithesis of what Scrum does, it renders your planning utterly pointless, breaks all your Scrum reporting, and stops you from ever being able to improve.

If you genuinely are working in a way that takes new work into a sprint automatically, without planning, then I'd very strongly recommend that you stop pretending you're an Agile team, and move to either a Service Desk project or a Kanban board, where you do "drink from the firehose".

That said, yes, you can break your Scrum with Automation. Set up an automation that triggers on "issue created" and edits the current issue, setting the sprint field to something (you've got a number of options there, I don't need to explain them here, the drop-down is clear!)

comments: author: Rajesh Shetty
body: Hi Nic,  
Indeed..! I accept you suggestion and consequences if we do that.  
Fortunately I has to do it, as it a customer requirement.

Please suggest if you have solution for Automation rule.

Thanks in advance.


author: Nic Brough -Adaptavist-
body: I'm afraid you need to go back to your customer and tell them their "requirement" is, well, to be diplomatic "non functional". It's simply going to break everything and they should not do it.

Tell them that the better options are to stop doing sprints and adopt a queue-like system. Scrum is not right for them, obviously.
Is it possible to @ a specific user in a comment that part of an automation rule?
Asked by Jayme Burkhalter:

If a comment is added as part of an automation rule, can I add an @ for a specific user to be notified of the change?

I have only been able to find how to mention someone like the Assignee, or Creator, or Reporter.

Use case:

As a portfolio manager

Who is not necessarily an Assignee, Creator, or Reporter,

I want to be notified (in the comment) when a Feature/Epic is auto-closed by an automation rule, so I can prepare to release that Feature and notify stakeholders of the full completion of the Feature


Answers:
author: Mikael Sandberg
body: Yes, it is possible, but you have to use the markdown text and know the user's AtlassianId in order to do it like this:

\[\~accountid:{{issue.assignee.accountId}}\]

comments: author: Darryl Lee
body: BTW, to find your account ID or those of others:
> The easiest way I've found to find my accountId is to click on my icon on the sidebar and then on the "Profile" link. In the URL you can find your accountId after the last "/" :

Per [@miikhy](/t5/user/viewprofilepage/user-id/449205) here:

<https://community.atlassian.com/t5/Jira-questions/where-can-i-find-my-Account-ID/qaq-p/976527>  


author: Jayme Burkhalter
body: [@Mikael Sandberg](/t5/user/viewprofilepage/user-id/853579) thank you! so i tested this out but i think i had some trouble with the code in the brackets...i wrote it like so:

\[\~accountid:{{issue.assignee.myaccountidhere}}\]

and the comment that was left resulted in this:

\[\~accountid:\]

Am I meant to put my account id in the front or in the issue.assignee.accountid portion? or both?

(note: "myaccountidhere" is meant to represent my actual account id number)


author: Mikael Sandberg
body: You should not add your actual ID if you are the assignee, you should then use what I added above:

\[\~accountid:{{issue.assignee.accountId}}\]


author: Mikael Sandberg
body: The only time you would replace the smart value with the actual account ID would be if the user you want to @ mention is not in a user field on the issue. But if you have a field for lets say, stakeholders, the markdown text would be:

\[\~accountid:{{issue.Stakeholder.accountId}}\]


author: Darryl Lee
body: From my reading of [@Jayme Burkhalter](/t5/user/viewprofilepage/user-id/4387886) 's original post, he wants to @ mention
> ... a portfolio manager
>
> Who is not necessarily an Assignee, Creator, or Reporter,

So yes, if there is a Portfolio Manager field, then this should work:  

```
[~accountid:{{issue."Portfolio Manager".accountId}}]?
```

But if they're actually trying to "hard code" a specific user then it should be:

\[\~accountid:**JaymesAccountid**\]
Is there logic to have a field populated with the next unreleased version that ends in ".1"?
Asked by Davielle Boyce-Hotz:

I am looking to utilize an automated rule that will populate the next unreleased version (that ends in ".1") into the fix version field, upon being transitioned into a specific status.

Presently, our Fix Version releases have naming conventions that are labeled as "v.3.55.1", where "v.3.55.2, v.3.55.3, etc." would be hot-fixes. In the rule, the goal would be to have the field populated with the next unreleased version that ends in ".1", in order to avoid the issue being updated with a hot-fix version.

The logic to pull in the next unreleased version exists, though it does not address the issue in which we are attempting to resolve. I am hoping to receive feedback in reference to how to have the version selected based upon the criteria of ending with ".1"


Answers:
author: Bill Sheboy
body: Hi [@Davielle Boyce-Hotz](/t5/user/viewprofilepage/user-id/4999619) -- Welcome to the Atlassian Community!

Short answer: no.

Longer answer, and possible work-arounds:

In Jira, the "next unreleased version" is the one at the bottom of the list in the release/version list (without changing the sort order in that view). If your ".1" version is at the bottom of the list, you could find it just using the built-in rule features.

If it is not the "next" one, and there is one-and-only-one unreleased version with a ".1" at the end of the name, you could call the REST API to get all versions for the project, using a rule's web request, and then filter to find the correct one.

Otherwise, this may not be possible as I do not believe you can access the ordering of the versions from outside of the user interface with out-of-the-box Jira features. There might be a marketplace addon which can help with this.

Kind regards,  
Bill
Update a field value based on the parent issue same field value updated
Asked by Carin Talero:

I have a custom field = "Source", when an Epic Source field gets updated, I want to apply the same new value to the Source field of all the child tickets. How can I create that rule?


Answers:
author: Dan Tombs
body: Hi [@Carin Talero](/t5/user/viewprofilepage/user-id/3996159)

This automation rule is really common and something we have a lot of. I have attached a screenshot which will help explain our rule. Hopefully this can then provide some context on what you have to do.

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

Just replace "Delivery Team" for "Source"

Hope this helps,

Dan

comments: author: Carin Talero
body: Thanks, will this make that the value of the field in the epic that was updated, the same field in all the child issues under that epic will get updated to the same value?


author: Dan Tombs
body: Hi [@Carin Talero](/t5/user/viewprofilepage/user-id/3996159)

Exactly that. if the value of the delivery team in the epic changes, then it will cascade down. You can put a condition in between the trigger and branch so that only changes to epics will continue.

You can also create a different rule so that when an issue is attached to an epic to immediately get the parent values. Change the field updated to parent link.

Hope this helps.

Dan


author: Carin Talero
body: Thank you!


author: vaughan.dickson
body: Hi.

How do you update the child field from a DIFFRRENT field value. I need to populate my child Affected Version field with the Fix Version field of the parent/Epic. The values can be the same but obviously the field s are not exactly the same field.
How can I automate the sum of the hours entered in the ORIGINAL ESTIMATE field of the tasks in the
Asked by Luciana G?es:

The ESTIMATE field displays the sum of the hours of the ORIGINAL ESTIMATE for each task, but the EPIC ORIGINAL ESTIMATE field does not display the sum.

How to create an automation rule so that in the EPIC ORIGINAL ESTIMATE field, it presents the value presented in the ESTIMATE field?

![Tela_1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/209534iB564A918574A9CF6/image-size/large?v=v2&px=999 "Tela_1.jpg")![Tela_2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/209535iEC97646AAAA54040/image-size/large?v=v2&px=999 "Tela_2.jpg")


Answers:
author: Bill Sheboy
body: Hi [@Luciana G?es](/t5/user/viewprofilepage/user-id/4922227)

You may do this summation with an Automation for Jira rule. Please see this post for more details: <https://community.atlassian.com/t5/Jira-Software-questions/Sum-up-to-Epic-the-original-estimate/qaq-p/1880764>

And also note: the Lookup Issues action in rules now supports all fields, including Original Estimate, so it is much easier to find this sum.

Kind regards,  
Bill


author: Luciana G?es
body: NOTE: I USE JIRA CLOUD
Automation Jira Server: Create issue & Create Sub-tasks are not available in New Action step
Asked by Veronika:

Hi Community,

I am trying to automate creating sub-tasks upon creation of an issue type Release but "Create sub-task", "Create issue" and several other options are not available for me (they are grey on the screenshot). Upon hovering over it says that "This is a Pro Component. Remove this component to reenable your rule".   
Jira Server, I am Jira Admin.  
Any ideas how to resolve this are much appreciated.

![Screen Shot 2022-08-03 at 19.46.09.png](https://community.atlassian.com/t5/image/serverpage/image-id/209281i6ABBEF2BF940CB42/image-size/large?v=v2&px=999 "Screen Shot 2022-08-03 at 19.46.09.png")


Answers:
author: Jack Brickey
body: Hi [@Veronika](/t5/user/viewprofilepage/user-id/1091315) , is your version of A4J PRO? If you are unsure can you check under the installed apps?

comments: author: Veronika
body: Didn't realize I am using a Lite version. Thank you!


Tags: jira-server
How can I access release attibutes within Jira automation
Asked by Martin Hechinger:

Hello together,

I am wondering how I can use release attributes in Jira automation like I can use issue attributes.

Specifically I am looking for "Release Date" and "Predicted completion date" of an release to send it via email.

Another option to generate a table with all these release dates would be also nice.

Thanks for any hints

Cheers Martin


Answers:
author: Bill Sheboy
body: Hi [@Martin Hechinger](/t5/user/viewprofilepage/user-id/4347047)

I believe that Release Date is a built-in field, and so you can access that one with smart values in an automation rules.

I am unfamiliar with "Predicted completion date"; is that something you are getting from an addon tool? And I do not believe that Version/Release supports entity properties, so perhaps no one added that: <https://developer.atlassian.com/cloud/jira/platform/jira-entity-properties/>

When you not generating a table of release dates, one way to do that with one of the marketplace addons for reporting, or to call the REST API from an automation rule, and then email the information.

Kind regards,  
Bill

comments: author: Martin Hechinger
body: Hi and thanks [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)

the predicted completion date is shown on the "Version Report" report metric below the graph. This value is calculated by jira somehow.

I do not get it to work with the REST API either. Maybe because I am useing Jira Software and not the cloud version ??

Best regards,

Martin


author: Bill Sheboy
body: Thanks for clarifying. I am not aware of a built-in way to get the calculated information from the Version Report...except by running the report.

I suggest looking at the marketplace for better release/version management reporting addons.


Tags: release
Add Attachment through automation after issue creation
Asked by Manish Arya:

HI All,

Can we add any attachment via automation, once JIRA issue is created I want to add one attachment after issue is created.

How can this be done?


Answers:
author: Fabio Racobaldo _Herzum_
body: Hi [@Manish Arya](/t5/user/viewprofilepage/user-id/4219380) ,

unfortunately, there is no way to manipulate attachment through an automation.

Fabio

comments: author: Manish Arya
body: I can see delete attachment option is there but not add attachment that is strange :(


author: Fabio Racobaldo _Herzum_
body: Adding an attachment is not a feature provided by an automation


author: Karyna Tyrnavska _SaaSJet
body: Hi, [@Manish Arya](/t5/user/viewprofilepage/user-id/4219380) !

You can solve this case using [Smart Jira Forms](https://marketplace.atlassian.com/apps/1227085/forms-checklists-for-jira?hosting=cloud&tab=overview&utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_Add-Attachment-through-automation-after-issue-creation_20220804) add-on developed by my team. It allows adding a form to the issue when it\`s already created. But you should do it manually.