Mikael Sandberg Community Champion

Hi @Amy Rohan, Welcome to Atlassian Community! No, Plans is the new name of Advanced Roadmaps and there is no difference, just a name change.

Correct, you would have to add them as request participants, adding them as watchers will not work since that needs browse permissions.

It can be done, but you have to use a Jira Software project in order to do it. Our team is doing it for Tier III and Tier IV in order to plan internal projects. The filter for the board is bringing in requests from the JSM project if anyone from Tier III or Tier IVis assigned to it.

If that is not working then use the lookup object component and then use that to get the name like this: {{lookupObject.Name}}

{{issue.<assets field name>.Name}} should do it. The asset selected is your object and then you just use the . function to get to the attribute.

If you need to keep a record, I would assume other then just the history, you would need two fields for this. This is something similar to the approval process that I wrote about here. Here is my solution for it... Create a new screen that has the reason for failure field on it. Assign that screen to your new transition.…

Here is a good overview of how the different schemes are linked to each other, https://confluence.atlassian.com/adminjiraserver/project-screens-schemes-and-fields-938847220.html I know the KB is for DC, but the same thing applies in Cloud.

Hi @swaroop reddy, Welcome to Atlassian Community! Correct, currently it requires that you select a specific team, smart values cannot be used for it. You could work around it by having an automation for each team that is triggered via a incoming web request and then use a dispatcher automation that is using the IF/Else…

You should be able to do this via automation and trigger it on issue change for the issue type. You can then check if the initiator have the right permissions and if not then change the issue type back. Please note that this would only work if all the issue types in your project are using the same workflow, if not then you…

Since you mentioned that the task is created by another automation, make sure to go to Rule details and check "Allow rule trigger"

The most cases I have seen for KBs are all public ones, I know IBM was having theirs behind access control linked to your license, but I think that solution was their own. The only option that I can think of would be to use JSM, but the KBs that you can present on the portal is limited before the user have to search for…

Hi @Daniel Elias, Welcome to Atlassian Community! It depends, your license plan allows you to add up to 5 guests for each license you have, see this article for more information. The limit is that guests can only have access to a single space. So if your Knowledge would be under one space then this would work. But if you…

Hi @Rogerio Oliveira, Welcome to Atlassian Community! Free plan products that are inactive will be deactivated after 120 days, so based on your description that sounds like this is what happened in your case. You can learn more about the retention policy here. Once your instance is getting close to be deactivated you…

Hi @Ly, Tai, Welcome to Atlassian Community! A couple of things that you can try; use a incognito window and see if that works. If you are using Chrome they have been releasing new versions of it about every week since they announced that they are changing things for 3rd party cookies, so try and clear your browser history…

Hi @ryusei arai, Welcome to Atlassian Community! I haven't seen a public statement yet from Atlassian regarding Opsgenie, but based on the KB you linked above and what I have seen from the roadmap for JSM everything indicate that Opsgenie will be integrated into JSM and not offered as a standalone application. This is just…

Hi @Marie-Anna Pate, Welcome to Atlassian Community! The short answer is no, you cannot edit the issue key in a sequential order. The issue key will be the next available number for the project and you have no control over it.

You are correct, the answer is no, team-managed projects cannot use workflows from a company-managed one. TMPs should be seen as its own island with no connections to the outside world.

Hi @William Elton, Welcome to Atlassian Community! It sounds like the resolution is not set when the request is moved to Completed and that would explain why it is still shown as open to the customer. When you open up a completed request, do you also see something like this? The checkmark and Resolved is the resolution and…

This can be done, what you have to do is remove the browse project permission for those users. The drawback of doing this is that you will not be able to mention users unless they are the reporter or request participants on the issue when you reply to them.

In order to add the new field and make it required for only one issue type you need to create a new field configuration. If you go to Settings > Issues > Field configuration. From here locate the one that is currently used by the project and copy it. Once you made the field required, you need to associate this new field…

Each column can hold multiple statuses, it doesn't have to be a 1-to-1 mapping. Go to Board settings > Columns and from here you move your statuses to different columns. There is no linking other then the column, so in order for the board to consider Maintain as a done status (this is different from the status category) it…

Hi @McKenna Hogan, Welcome to Atlassian Community! Is this new column the furtherest column to the right on the board, or is Done still it? The board will only consider issues that is in the furtherest right column as done. If you have multiple statuses that should be considered as done, as in your use case, then you have…

My guess without seeing the descriptions for both would be that they both contain "Design elements" and "Analysis" in the description field and that is why you get all 10 subtasks. When using the contains condition, especially on multiline fields you have to be very specific in what you are looking for, since if you are…

Hi @Hazel Edmends, Welcome to Atlassian Community! You have a couple of options, one is to copy the rule that you have and then just make the changes needed for it. Another option is to utilize the if/else condition and base that on the description. A third option would be to use a dispatcher, basically what it does is…

Hi @Hippolyte Simon, Welcome to Atlassian Community! Slack no longer support @username so you have to use their member Id. Have a look at this article that describes how you can add users Slack member Id as properties on their accounts. 

And yes, basing the project on an existing one is similar to selecting a template. The difference is that you will share the configurations when you base it on an existing project, meaning that if you change the workflow it will affect both projects.

If you click on Jira under Products you should see the bug tracking template. The new bundles are related to the merging of Jira Software and Jira Work Management.

No, forms cannot be visible from the Create issue screen, you would either enable the generic URL from where you can create issues, or after the issue is created you add the form to it. If you need it to be visible from the Create issue screen you would need an app like scriptrunner or one of the other scripting apps…

We had personal spaces but I decided to disable them and the reasoning was their spaces are not archived/deleted when the are leaving the company which lead to us having thousands of spaces by former employees. Another reasoning was that people clicked on Create from the home page in Confluence, resulting in adding pages…

Hi @Allen Chen, Welcome to Atlassian Community! You can achieve this by using Forms on your request, it has an option to add Other and if selected the customer is prompted to enter a value.