Comments
-
See if you can find one that is called "Copy the comments from the original work item to the cloned work item", this is what it looks like and should be exactly what you are looking for: The {{OriginalComment}} smart value in the branch is assigned {{lookupIssues.last.comments}}.
-
Hi @borsitsb, Welcome to Atlassian Community! If you look in Automation Templates you will see a rule called "When a comment is added to a linked work item → Add the comment to other work item" that you can use as your starting point. Just change the link type that the branch is looking for.
-
You cannot add the Request Participants field to the request form. What you need to do is allow customers to share requests under Space settings > Access > Customer permissions.
-
In the Space Settings > Channels & self-service > Knowledge base, have you set the view permissions to Everyone? See this KB for more information. The KB also has a link to a suggestion to allow you to browse your Knowledge without searching or using categories that you can vote on.
-
Hi @Emiliano Reynoso, Welcome to Atlassian Community! This is expected, any groups that are synced from your IdP cannot be changed on the Atlassian side, you have to make the change in your IdP. You can only manage groups that are locally created in Atlassian.
-
I am pretty proud of this one, because it captures what Thor was like. He loved being at the park across from our house and make sure that the kids behaved while playing.
-
You do not have to add new groups to a group picker fields, it will be populated by the groups you created on your Atlassian Instance, sort of similar to how user picker fields works (example reporter and assignee).
-
My very first one was part of the Dragon Slayer Quest back in 2009 (still have the t-shirt :)). My very first one in my professional world was in end of 2012, I had just set up Jira on a Windows server and connected it with Jama Software and was syncing some requirements over as part of a proof of concept.
-
It all depends on what type of project you are. using. If the projects are team-managed then project admins can create fields that they want. But if you are using a company-managed project then you have to be a Jira admin in order to create new fields. Your other option is to use Forms, that would allow the project admin…
-
Hi @Jennie Miller, Welcome to Atlassian Community! It sounds like the Udemy course is outdated, the menu on the left hand side is the current navigation that was rolled out the summer of 2025. The announcement can be found here. There is no way of changing back to the old navigation with the drop-down menu.
-
The Assign work item component in Automation allows you to assign the work item to a user in a group, and the method can be either Balanced, Random, or Round-robin.
-
Hi @rafael_arias, The short answer is no, you cannot change the status category, those are hardcoded values.
-
If you go to Settings > Jira apps and then Email requests under JSM you have settings to strip quotes and hide email signatures. You can also add custom test that it should detect and hide.
-
Hi @ahcorso, The Atlassian support team that is on here has been notified and should reach out to you within 2 business days.
-
Hi @Krupa Nagabhushan, Welcome to Atlassian Community! This is a question for the Jira admin for the ONAP instance. This community is mainly made up of Atlassian customers and as such we do not have access to other customers instances.
-
The URL it is looking for is your workspace Id, and it should looks something like this: bitbucket.org/workspaceid When you log in to bitbucket that is the first part of the URL.
-
Hi @Kenn Roberson, Welcome to Atlassian Community! The Forms submitted trigger is related to JSM Forms, it cannot be used with forms that you create in Jira, those are different features. JSM Forms are based on an app called ProForma Forms that Atlassian acquired a couple of years ago, while forms in Jira is an in-house…
-
You have to configure Confluence to allow anonymous access in order to be able to change the settings in JSM. In Confluence you have to global permissions and enable it. Have a look at this KB for more information.
-
No, there is no component in Automation that would trigger on new watchers added, you would have to create a webhook and an app in order to do that.
-
I would start by contacting your IT Helpdesk, they should be able to direct you to the right person.
-
That error indicate that you do not have a Confluence license assigned to you, so you would have to contact your Confluence admin to get access to your instance.
-
When you click on you avatar in Statuspage and select API info and then click on Create key you should see something like this: Could it be that it defaulted to No expiry when you created your key? As far as I understand it that option will be removed in a couple of days and you would only see Expires on and the date…
-
Here is the bug for the Slack DM component, JSDCLOUD-17865. It has been closed but based on the comments there are still some issues with it, and if it works it only works to send DMs to the user. For @ mentions you currently have to use the Slack member Id and then the message would look something like this: <@ABC123456>…
-
You would need to know the Slack Member ID of the person you want to @ mention. There are a couple of ways of doing this, check out this article of one way. At my previous job I created the user property with the member Id when the user was imported from Okta the first time, including some other information we used like…
-
Yes, your automation can trigger on subtasks created, just treat is as a regular work item. Then just add a condition that checks if the work item is a subtask.
-
The only option you currently have would be to use a select field in Forms and manually enter the work items that the project have and then use automations to set the correct work item when the form is submitted.
-
If you are on a standard plan that is all you can do, besides setting restrictions on each request type. If you are on premium plan or up you can create help centers that you can configure to limit what is available on it.
-
Does the project in the new instance have the same work item types as in the original instance? Based on your description it doesn't sounds like that so the automation picked up the first work item that is available in that space in order to save the automation without any errors.