Mikael Sandberg Community Champion

Hi @Andrew Katsewich, Welcome to Atlassian Community! You can report this to https://www.atlassian.com/trust/report-abuse and they will take action on it. 

Make sure that the user in question has a JSM license. the could be in the right role in the project, but if they do not have been assigned a JSM license they cannot be set as the assignee.

Hi @zslicense, Welcome to Atlassian Community! The community is mainly made up of Atlassian customer and as such we do not have any insight to other customers instances. You should direct your question to Support, support.atlassian.com. 

Hi @Bernice.White, Welcome to Atlassian Community! You have ended up here either because Verint or your company is using an Atlassian product. Because your question is regarding a non Atlassian product you should probably contact your IT Helpdesk and they should be able to answer it. Also note that I removed your email…

Hi @Bekkah.Crisp, Welcome to Atlassian Community! If you remove .fields. from the smart value that should give you the output like you are looking for. The smart value should be {{issue.customfield_11566}}. 

Just to add to @Joseph Chung Yin answer. If you are on the new Operations UI instead of Opsgenie you first have to go to the team and click on Operations, this will allow the team to be responders.

Unfortunately the advanced search cannot differentiate between the phrase being part of a list or not. But since you are using an automation you could do this smart values for text to check the length of the value to see if it is part of a list or not. You could also use match or split to do that.

Here is another option. Instead of using Assets you could use a JSM project for it and use that as part of your automation. It would work similar to Assets were your automation would check if there is a OOO request and if so update the assignee.

You can search a text field for specific words or phrases by using the advanced search like this: myField ~ "\"my phrase\"" It this case it would only return issues with that specific phrase in the field, it would not return issues that has just my or just phrase. I use this in automations that checks for specific words…

Correct, issues will get the new value automatically, but for reports and automations you will have to manually update those. Issues are using the internal number for the value, but reports and automations are using the display name.

Hi @me, Welcome to Atlassian Community! If you go to support.atlassian.com and select Billing in the contact form that team should be able to help you.

The short answer is no, there is no settings within Statuspage that would allow you to make other fields mandatory. One option would be to use Jira/JSM to create the incident message and then use automation and the REST API to work around it.

And to add to @Marc -Devoteam- answer, Atlas is going away as a separate product and will be part of the Cloud platform in the near future.

Hi @Carmine Pezzella, Welcome to Atlassian Community! It means that you can assign the JSM license to X amount of users, it has nothing to do with how many agents are online. So if you have 10 licenses you can have 10 agents, even if only 4 agents are working at the same time. 

Another possible solution would be to use Assets for it. You could then have a request type for OOO that creates an entry in Assets which is then used in your round-robin automation to see if the assignee is OOO or not.

You could use the on-call schedule in Operations to do this. If you have multiple users on-call at the same time you would need something like tray.io in order to do it, I wrote about it in this article.

Hi @Natasha Vieira, Welcome to Atlassian Community! Make sure that the user in question has been assigned a JSM license. The error you see usually happens if the user do not have the right license, even though they have been added to the right project roles. 

Do you have users that have been added with the Role Trusted or Site admin? If you do they will automatically get access to all products that you have, but they are not part of the user count when you look at the product tab.

True, you can now set restrictions on request types, but that only works for managed users that belongs to the group(s) that should have access to the request. This does not work for JSM only customers, since they cannot be added to a group.

Hi @Raman Ramanau, Welcome to Atlassian Community! No, currently that is not possible, you can only use it within Confluence at the moment. 

Hi @Alex Wilson (TMNA), Welcome to Atlassian Community! Sprints are not board specific, and this happens if one or more issues on your board has been associated with a sprint on another board. Usually this happens if users are assigning the sprint directly from within the issue instead of using the backlog to assign issue…

Yes, I have multiple automations were I needed this, and the way I solved it was by using a main automation as the dispatcher that then calls other automations via the incoming webhook trigger. It does increase the number of automations you have, and knowing which one calls another one can get confusing if you do not have…

Hi @Martin Quezada, Welcome to Atlassian Community! Unfortunately this is not possible. The portal groups are not stored as part of the request, and therefore there is no way of finding out from which group the request was created in. You only option would be to make request types portal group specific, you would then know…

If you do not set a start date and only set the due date it will show the issue on that date. When you fill out both the start and due date you will see it spanning that date period. There is no other settings that can be made to only show the due date on the calendar.

Hi @David Donofrio, Welcome to Atlassian Community! This community is mainly made up of Atlassian customers and my guess is that you ended up here because of the use of Bitbucket. Is this the repository you are referring to, https://bitbucket.org/cjdskunkworks/meadeautostar497/wiki/Home? If so then it looks like there are…

Hi @wahidunnisa saiyed, Welcome to Atlassian Community! You read the KB wrong, As of Bamboo 8 Mercurial is no longer supported. Starting on Bamboo 8.0, support for Mercurial has been discontinued and the Mercurial plugin was removed from bundled plugins. 

Hi @Susy Lopez, Welcome to Atlassian Community! Currently that is not possible without an app. There are multiple ones in the Marketplace that can do this, like Mantra and Refined.

The report includes issues that were added after the sprint was started. They will be marked with a * so that you can identify those issues. 

Correct, if you update the existing scheme by removing an issue type you will be asked to transfer existing issues of that type to a new one. A project cannot have issues that are linked to an issue type that is not defined in the issue type scheme that the project is using. 

There is an active incident for this, see https://jira-software.status.atlassian.com/incidents/lb04yjdct854