Mikael Sandberg Community Champion

In case someone else is running into the same issue, the cause of this was that there were a hidden whitespace at the end of the smart value. The fix is to use the .trim() to remove it and the automation is now working as expected.

In order to know the request types that is associated with an issue type you would have to get the issue types and then use the issue type Id to compare that to the result from Get request types/Get all request types. But when you create the request via Create customer request you do not need to know the issue type, all…

Hi @Sourav, Welcome to Atlassian Community! Please make sure you are using the API for JSM to create your request, that is the only one that can set the request type. If you are using the API for Jira Cloud you cannot set the request type and have to manually do it. 

Hi @Daniel Tapia, Welcome to Atlassian Community! No, the original reporter would be be notified it you change the reporter to someone else. The notification will only go to current users, it will not check the history of the issue. Same thing applies if you would change the assignee or remove watchers/request…

No, Forms does not except data from a csv file, currently it only support JSON information via a data connection. There is a suggestion to add support for Google Sheets and csv, see JSDCLOUD-10852. I would recommend that you go and vote and follow that suggestion to see if Atlassian decides to add that feature.

Just to add, the only Atlassian license that includes Trello is Atlassian Together, which bundles Confluence, Jira Work Management, Atlas, and Trello.

You can also leave feedback to the product team about public links via this article.

Currently public links can only share a single page, not the page and any child pages. There is a suggestion to be able to share both the parent and any children with a single link, CONFCLOUD-73220 and I would suggest you go and vote and follow it.

Yes, the form is added to the request under the attached forms section: No, you cannot query on the attached form, but if you want to get data out of the form you can use the API to get the answers, or link the fields to Jira fields and filter that way.

No, the recalculation of SLAs only happens on tickets that have an active SLA, it will not be recalculated on any resolved/closed tickets.

This is expected, edit restrictions are not inherited down from parent to child pages. Please see When content is inheriting restrictions from parent content for more information.

Those buttons are part of your workflow, so to edit those you have to edit the workflow that is associated with the issue that the request is linked to.

The way I do it is that I check for a specific link type that I use when creating additional issues, and if they exist then the automation will not execute past that check. You can also add something in the summary field of the issue that you create and check if that issue already exist if you do not want to use a specific…

Hi @Daniel Corrales, Welcome to Atlassian Community! Yes, this can be done with automation, and if you look under the Templates tab you will find a rule called "When all sub-tasks are done → move parent to done" that you can use as a starting point. If you do not need it to check all subtasks if the parent should change…

Hi @CA, Welcome to Atlassian Community! No, an issue can only have one parent, but you use issue links to link an issue to multiple other issues. 

Hi @Phillipe Ino, Welcome to Atlassian Community! One option is to start using the new Teams and then use the Team field to assign issue to the 4 teams. This would also allow you to filter on issues for each team.

You can do this by adding a new attribute, for example visible, and then use that in the field configuration to not show objects that have that attribute set. That is how I do if for our application access request, I have the visible attribute set to either yes or no, and only the ones that are set to yes are shown on the…

This can be done, but you would have to use the same request type and then have the user pick if it is an infrastructure or application issue. You can then use filter issue scope to set the affected service, which btw has to be a new assets field since you cannot modify the default one in JSM.

Basically you need a new custom field that is used for the approval/decline log, and I'm using a second one that I use in the automation to see which transition was selected. As part of the transition I have a post function that sets the field Approval to either approve or decline based on the transition. And the…

Correct, team-managed projects do not allow you to set the permission on the comment like you can do in a company-managed one. This is by design since team-managed projects do not have project roles.

Just to add to Trudy's answer. Native gadgets cannot be modified when it comes to colors, fonts, etc. For that you would need an app, we are using Custom charts for Jira but there are other apps in the Marketplace that can do this too.

Hi JA, It has been awhile since I used Jira DC, but I assume that the Project Health is a custom field you added, do you know what type it is?

Hi @Chris White, Welcome to Atlassian Community! Check your permission scheme for the project, by default project admins have permission to delete issues. Go to Project settings > Permissions and look for Delete Issues. 

Removing fields from the layout will not remove them from the screen that is used for Create issue. So you need to remove the fields from there too. Just go to Project settings > Issues > Screens and select the one for the create issue.

No, you will not be charged for enabling public sharing. Public links is a feature that is included and is intended to be used when you want to share a page with someone outside of Confluence without giving them access to your instance. Note that the public page is limited in what it can show, for example page tree and…

Hi @Ivan Gonzalez, Welcome to Atlassian Community! The first thing to check is if under Project settings > Details and see if the default assignee is set to Unassigned or not. If it is set to unassigned the next thing I would check is to see if on the request type you have added assignee as a hidden field on the request…

Hi @Filip Mitev, Welcome to Atlassian Community! Here is how I did this in a Work Management project where they wanted to be able to approve/decline independently and then make a decision on what to do once everyone approved or declined it. In the workflow for the status where the approval needs to happen I have two…

Before you disable the user you have to remove them from site admin. You can do that by going to admin.atlassian.com and then under Settings > Administrators you can remove the user from that list. Once that is done you should be able to disable the user.

@Martijn Lukaart There was an active incident earlier today that affected Jira that has been resolved so give it another try and see if it works now.

You should be able to see what is going on by checking the email log and download the raw email for those requests where the distribution list is not added as request participant. Any address in from and cc should be added depending on how your customer permissions is set up.