Mikael Sandberg Community Champion

I should have said the condition in my answer. The previous status condition will evaluate if the issue has been in a previous status or not, but you invert it so that you can prevent the issue going back to that status Here is an issue that is using the above condition, it is currently in the In progress status and I have…

Yes, that is possible. You can either use the previous status validator, or the other option is to disable the global transition and instead create a transition from for example To Do to In Progress.

Yes, that is possible. And then all you need is an automation that will set the assignee based on the value selected. To create the field just go to Settings > Issues > Custom fields and create it from there. 

Hi @Alicia Johnson, Welcome to Atlassian Community! It could be that your email address has ended up on the suppression list and that is why you are not receiving any emails. You should have your admin contact Atlassian support and they can verify if this is the case and removed you from the list.

Hi @Suporte Tecnologia, Welcome to Atlassian Community! The portal group is not stored anywhere and cannot be used to find out where the request were created, so your only option is to look at either the request type or the organization that the reporter belongs to in order to identify who should be assigned the request. 

No, you cannot disable the Virtual Agent for specific people, but if you need to add a message to the channel without creating a request or involve the VA you can use the :mega: emoji

Okay, so then going to the billing section under admin.atlassian.com would be the way to go. 

Hi @Jim Hagen, Welcome to Atlassian Community! I am so sorry for your experience. Do you know if you are on a monthly or annual subscription? If you are on a monthly subscription you do not have to do anything. If you are on an annual subscription you can go to admin.atlassian.com and then under Billing you can managed it.…

Hi @Janet Barton, Welcome to Atlassian Community! Yes, you can enable the new Platform experience on your sandbox only, the feature is provisioned per site. That is the set up I have in our environment.

Hmmm, the only thing that comes to mind wound be an app that is doing it, based on the error message that you get when trying to remove it... Maybe try and create a new test request type and see if the same thing happens with it?

Do you have an app that added the Maintenance Start Time? That would be my guess and if that is the case then there is not much you can do if that app needs to have the field on the request form. you will still see the field on the issue view once the request is created. The only other thing that I can think of if you…

Yes, since sprint is a system field and if it is not on your issue screen already then you would need Jira admin permissions in order to add it to the issue view.

It could be that someone moved it from the issue view to the request form. Once a field is on the request form you will not find it when searching for it on the issue view, but all fields listed in the request form will be present on the issue view. If you want to move it from the request form to just be on the issue view,…

Hi @Robert Smith Welcome to Atlassian Community! Sprint can be added to your request types, all you have to do it go to Project settings > Request types and under Issue view you can search and add the sprint field. We do something similar, our team is divided into Tiers and for Tier III/IV we organize our changes coming in…

Hi @Nico Masor, Welcome to Atlassian Community! During Team 24 Atlassian announced that Jira Software and Jira Work Management is now combined under the single name Jira, and here is the blog post that announced it. To create a Work Management project all you have to do is go to Projects > Create project and select the…

Is the Product category a cascading select field? If that is the case then you would have to parse out the values selected, because if you just use {{issue.product category}} it would return something like this: {self=https://your-instance.atlassian.net/rest/api/2/customFieldOption/10028, value=Hardware, id=10028,…

If the list is predefined then it is either set on the request type or via an automation. So go to Project settings > Request types and then locate the request type in question and on the Request form look for the Request participants field. If that field is hidden you can define default values for it.

Hi @Prasad Jayawardena, Welcome to Atlassian Community! If you hover over the person that you want to remove from the shared with you should see an X, clicking on that will remove the person from the list.

Hi @Lucy Chien, Chialing, Welcome to Atlassian Community! You have ended up in the community for Atlassian products, most likely because the application you are using uses one of Atlassian's products. 

It can be done, you would need the app Dev Info for Jira in order to do it.

You would to create pre-receive hooks in order to enforce the commit message format, or there are apps in the Marketplace that can enforce the format and check the status of the associated Jira issue. 

Correct, in a team-managed project the board is integrated in the project, and you cannot have multiple boards in a team-managed project either. Once you created a team-managed project you can change it between scrum and kanban by turning off sprints. Note that team-managed projects are limited in what can be done in them,…

Hi @Michael Reed, Welcome to Atlassian Community! You would need an app in order to do this, I have used Scriptrunner in the past to do something similar. Check out the Marketplace for other apps that can do this, there are scripting apps and external data apps that can achieve this.

Okay, because you included the screenshot of the time tracking feature I assumed you tried to use those date fields. So are startTimer and endTimer both variables? The reason that {{startTimer.plusBusinessDays(3)}} is not working could be that you need to convert it to a date format that Jira understands. You could try and…

A board is separate from the project, the only relation it has is that it is located under a project. What controls the board is the filter that it is using and you could create a board in project A that is only showing issues from project B or vice versa. When you create a board and select Board from an existing project,…

To expand on team-managed projects and boards; a board can only live within a company managed project, but once you have created it you can modify the filter used by the board to include any project, including team-managed ones.

Okay, if you go to Project settings > Request types and then under the Incident category select the request type you want to change. The go to the issue view tab and you will see those fields listed, just drag those fields to the right and they will be removed from the layout.

Hi @Victor Fernandez, Welcome to Atlassian Community! Could you give a bit more context on what you are trying to do? Where do you want to remove Slack, Teams and Zoom? From a select field on a request type?

Hi @Jason Finke, Welcome to Atlassian Community! In its simplicity your automation would look something like this: In this example I am using the smart value compare because my sandbox do not have a product category field, but you can change the if to use the issue field condition instead.

Team-managed boards cannot be deleted without deleting the project. the board is integrated with the workflow and the only way to manage the workflow is from within the board.