Mikael Sandberg Community Champion

This should be pretty straight forward, here is an example of the post function from the default ITSM workflow that clears the Resolution field when moving from Resolved back to In Progress: Just make sure that you set the Resolution field to None, that will clear it.

As the error message is stating you have to create a request type that have both the summary field and the description field as visible fields on the request form like this:

You need an app that extends JQL in order to do that, out-of-the-box JQL cannot do nested queries. I know that Enhanced search/Scriptrunner and JQL Tricks can do this, but there are also other apps in the Marketplace that can do it too.

We used to manage everything within the automation, so if someone was on PTO/sick leave/etc the automation had to be updated accordingly. Now we are using the on-call scheduler in Opsgenie. Unfortunately automation does not support if you have multiple users on-call at the same time, so I am using tray.io to get the list…

You should be able to do this using automation and smart values. Here is an example of an automation that checks the hour the issue was created and logs it in the audit log before assigning based on the on-call schedule that we have in Opsgenie: To check the day you can convert the date to the day like…

There is not function in JQL that would allow you to do do this, and I don't think any of the apps that extends JQL has a feature for it either. What you could do is have a custom field that keeps track on the number of sprints the issue has been in and then have an automation that updates that field every time a new…

Hi @Alakbarov, Eldar, Welcome to Atlassian Community! In order to change between issue types that are using different workflows you have to use the move option to do it (assuming that you have move permission in the project). In the issue detailed view, just click on More > Move to start the process. 

Okay, so on standard plan the nested archiving is not an option, you need to be on the premium plan in order to have that feature. This KB has more information about it.

I'm just a customer like you, so the the only information I have is based on Atlassian's public roadmap and it looks like it is scheduled for Q2 2023.

Hi @David Shapira, Welcome to Atlassian Community! Based on the info in this KB Atlassian does not yet have a timeline on when the public link will be back, but fingers crossed that it will happen sooner rather then later.

Based on a quick look at the Marketplace listing for AssetIT you can use that with both JSM and Jira Software. But I do not know if ScanStar has an integration to it, that is something you need to ask RightStar about.

If you look at the first screenshot from the "Label gathering studies..." on the Share screen you can see that there is a restriction on it. So start there and go up in the page tree to find which page has a view restriction that is inherited down.

When you archive a page that have child pages you will be asked if you also want to archive the children too:

That's possible too, the reporter was just an example. For example, I have an automation that looks for a specific text within the description that is then used to find duplicate issues. You could also use a custom field to specify the user, either a user picker one or a text field.

You need to be a org/site admin in order to see those options, and you can check if you are by going to admin.atlassian.com. Here you should see your org and be able to manage users and products.

Hi @Gaurav Bedi, Welcome to Atlassian Community! RightStar has a product called ScanStar that integrate to JSM Assets and allows you to scan a bar code/QR code via a phone. We looked at it about two years ago but decided to go a different route, but we may revisit that again soon.

I know Adaptavist has a script library that you could check out, https://library.adaptavist.com/?_ga=2.16033461.2020747712.1679415481-2123515169.1679415481

You cannot do this with automation, it cannot pre-populate the comment without posting it. You would need an app like Behaviours, Dynamic Forms, or Power Scripts in order to do it.

You need to check the permission schemes used by the other projects and make sure that Create issue isn't set to "Application access (Any logged in user)" which is the default permission.

Hi @Philipp Brunnbauer, Welcome to Atlassian Community! Confluence has three levels of permissions; global, space, and page restrictions. What is preventing the user from seeing the sub-page is page restrictions. View restrictions are inherited down from parent page to child pages. As you can see in the Inspect permissions…

Hi @Laura Rodriguez, Welcome to Atlassian Community! The automation should be fairly easy to create, something like this would do it:

One way of doing it is to use replace, like this: {{issue.summary.replace("<user>","{{issue.reporter.displayName}}")}} Another option would be to use substringBefore.

Yes, and no. The summary has to be set when the issue is created, and automation runs after that happens. So what you could do is set a default summary, and then have an automation that triggers on issue create that edits the summary to something else.

Looks like the link was duplicated when I posted it, here is the correct link, https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562

You can use the official Jira Cloud for Google sheet app to import Jira data into sheets. Note that this is only one way from Jira to Sheets, if you also want to update Jira with data from Sheets then you need to look at one of the other apps in the Marketplace that can do this.

Based on the history it looks like Resolved is in the status category In Progress, and that is why it says that the status category changed on 3/1 because In progress is in that category as well. You would either have to change the Resolved status to the Done category, or use a custom field that sets the date when you move…

This should go away soon when Epic name will become optional, here is the original article from last year outlining the changes that are coming to Epics, and if the timeline is still the same this should happen around 3/22, so starting next week.

Hi @Pradeep Prakasam1, Welcome to Atlassian Community! The number of licenses for an app has to be the same that you have for the Atlassian product, so if you have 700 JSW users you have to get 700 licenses for the app. Please see this FAQ for more information, Which license do I choose when purchasing an app?

You can also find which screen it is if you go to Settings > Issues > Screens:

Hi @Bianca BLAJAN, Welcome to Atlassian Community! You need to edit the screen associated with the transition to Pending and add the Pending field to that screen. You can see which screen it is if you click on the transition when editing the workflow, it should show you something like this: