Mikael Sandberg Community Champion

Yes, it is possible and assets do have actions in automation that you can use, one of them being lookup objects that you can use in order to create your automation. You can then use the advanced branching to iterate over the returned objects to create a sub-task for each one. It would look something like this: Note that is…

Yes, it is possible. What you need to do is get the Atlassian Id for the deactivated user, which you can do by going to Teams and lookup the user, or via admin.atlassian.com. You can then use it as part of your query like this: watcher = <atlassian Id> e.g. watcher = 1111122222333334444455555

Hi @WHITE WILLIAM, Welcome to Atlassian Community! You would need an app that extends JQL in order to do a nested query in order to get the result you are looking for. There are a handful of apps in the Marketplace that can do this. I have used Enhanced search and JQL Tricks in the past for similar filters.

Hi Veronica, Welcome to Atlassian Community! My guess is that it is your IF condition that is stopping your automation. Instead of comparing two values use the CQL option instead and set it to this CQL: label = 'to-be-archived'

Okay, then you have to create the issue type in each project, since team-managed project cannot use global issue types. Team-managed projects are like its own island with no connection to the outside.

Hi @Hailey Goodner, Welcome to Atlassian Community! This should be its own question. What type of project are you using? Company-managed or team-managed? If you are using a company-managed project you have to make sure that the issue type scheme that the project is using has the new issue type in it. Just creating a new…

Hi @Kirill, Welcome to Atlassian Community! In the board list, scroll down until you see Other boards and click on View all. That will bring you to a page that shows you all boards, and from here you can filter on the board you want to delete and then click on the three dot menu on the right and you will see an option to…

You can do this by using Forms in your request type. Forms allows you to add sections that are only visible based on what the customer selected in a previous field.

Hi @Joshua Mathews, Welcome to Atlassian Community! There are a couple of ways to make a field required. One is to set the field as required in the field configuration that you can find under Project settings > Fields. another way is a condition in the workflow that makes the field required. In JSM there is a third option…

Hi @Damian Parker, Welcome to Atlassian Community! You should be able to do this with the If condition and the smart value condition which has an option for regular conditions. R\d{5} would be the regex you want to use, since this would get R followed by exactly 5 numbers.

No, JQL does not have a feature that allows you to capture data between text, this is only possible in automation and smart values.

Hi @Maryanne Russell Samuels, Welcome to Atlassian Community! If your question is about how to set up SLAs then please have a look at this resource, Create service level agreements (SLAs) to manage goals. 

Yes, all you have to do is go to Project settings > Issue types and from here click Actions > Edit issue types. On the next screen you can move the issue type from the left column ( issue types available to the project) to the right column and then click save.

@Tschilar, Stacey It should work even if the text contains colon, I have a parser that convert an email from Workday to extract data from it and it has colons in it. Does you comment that you are parsing by any chance contain white spaces/new lines in the part that you are trying to parse? And what are you doing with the…

Hi @dusa navin, Welcome to Atlassian Community! The free version of Jira will always be free for 10 users, you have an option when you sign up for it that you get access to the standard version for the first 30 days as outlined in this FAQ. 

Mangrove forest 

No, if you hide all request types then you will see that message, the only way around it is to have a request type that is visible to customers.

You can do this via automation that checks when the issue was created and if it falls within those days and hours send the email. This would be similar to the automation that I mentioned in this article, Assign requests to agents based on the hour of the day/on-call schedule. What you would have to add is a check for the…

The Form does have a generic URL, but you can only use that if you have been assigned a Jira license. So if you want customers/users that do not have a license on your instance then the only way of doing that is what I mentioned above.

That is expected, you need to have a reporter on the request, so there is no way around it.

Hi @Ghata Singhal, Welcome to Atlassian Community! The only way to remove that message is to enable a request type to be visible in the portal. If you only want to display the form then associate that form with the request type, set the default value for the Summary field and hide it. Then when the user goes to the portal…

I would have to disagree with your opinion, to me it is an advantage that Atlassian gives you the basic functionality and then you can tailor the products to fit your company. I have used other products that tried to satisfy every customer requirement and as a company you end up using just a small part of what the product…

In order to do that you would have to use an app in the Marketplace that allow you to set field level permissions, Jira do not have a feature like that out-of-the-box.

Currently there is no option to hide projects from the portal, there is a suggestion to add that feature that you can go and vote for, see JSDCLOUD-2007 

Hi @Travis Lindemoen, Welcome to Atlassian Community! You can transfer the ownership of the repository, follow the steps outlined in this KB in order to move the repository to a new workspace/account. 

The Releases field is a special one, it is associated with the Releases feature, so in order to remove that field you have to go to Project settings > Features and disable the Releases feature.

If you remove the customers that should not have access to the project from Project settings > People as Service Desk Customers they will not be able to access the project from the portal nor from submitting emails.

Okay, in that case you may want to take a look at Forms, it allows you to add read-only fields/text that is visible to the user.

Hi @Howon Kim, Welcome to Atlassian Community! Could you describe what you are trying to solve a bit more? Any request types that you have assigned to a portal group will be visible on the portal an customers can submit them. What type of data are you trying to capture? 

You can learn more about Atlassian's backup program here. They do a daily backup but that is so they can do DR if needed, this backup is not available to customers. There is an EAP for a backup and restore feature which should be available in Q4 2024 based on Atlassian's public roadmap. There are also apps in the…