Mikael Sandberg Community Champion

Hi @PLohitha S, Welcome to Atlassian Community! JQL out-of-the-box cannot do a nested query that would allow you to get all epics and their associated stories, unless you specify each issue key for the epic in the query. You need an app that extends JQL in order to do a nested filter. There are multiple apps in the…

No, you cannot dismiss that error message, but giving the Service Desc customer - Portal access browse permissions does not automatically allow external users to see the project. What controls if a customer can access the project from the portal is if they have been added to the project role Service Desk Customer under…

Assets (formerly known as Insight) is only available if you are on a premium/enterprise product plan.

Hi @ADMIN IT, Welcome to Atlassian Community! If you add Service Project Customer - Portal Access (the first option) to the issue security that will allow the Request participants to view and get notifications for requests that they are added to.

Yes, your automation will not take action when you are selecting Okta App or Microsoft azure AD because the way your automation is configured. It will only take action if you select Atlassian Project App or Atlassian Ticketing System since that is your first condition. If one of those two values are select in your field it…

Awesome, thank you so much @Skyler Ataide! 

The start date I am looking for is the custom field Start date that Jira creates, not the start date on the version which I believe is the one you are using above. Start date from the Project fix version table is empty in this JSM project since it is not using versions:

The way you have configured your automation it would fail on your first condition if Business Application is not Atlassian Project App or Atlassian Ticketing System and all the other conditions are ignored. You need to change the conditions to be if/else instead for it to work.

Hi @stanleye87, Welcome to Atlassian Community! I would start by checking out all the free trainings that Atlassian University is offering and go from there. Hopefully your company also have some initial documentation for you to read.

So for the scenario when you set the asset object field the previous screenshot covers that, just add the initial trigger which could be when the issue is created. For the case when you are copying attributes to a text field, in this case I am using the description field, it would look something like this: Note that I am…

Okay, based on your screenshot for the lookup component the AQL is incomplete. So lets start there. Is serial number entered when the request is created? Or is your only reference to the object the reporter? Since Komputer is an asset object field you do not have to do a lookup, you can just use the edit issue component in…

Hi Craig, Welcome to Atlassian Community! Atlassian has a new product that is currently in Beta, Beacon, that can alert when there is unusual activity in Confluence, like viewing a lot of pages in a short period of time.

Hi @Silverio Rodriguez, Welcome to Atlassian Community! I have notified the Community Support team that is on here and they should be able to help you to get all of this sorted.

And to add, in JSM you can only add Request participants to the layout when you go to Project settings > Request types. It is not available to be added to a screen.

Request participants is a JSM only feature that allows you to share request with other customers. Watchers in Jira Software is sort of similar which allows you to notify users when the issue is updated.

Something like this should do it: project in (project1, project2, project3) AND "request type" in (type1, type2, type3)

Hi @Raj Somaiya, Welcome to Atlassian Community! No, the burn down chart is only available in JSW projects. But there is a created vs resolved chart that you can use for any project. 

You can do this with automation. Just create a rule that sets the security level when an issue is created and is of the specific type.

Hi @Jenni Davison, Welcome to Atlassian Community! The reason the parent is not waiting for all sub tasks to be done is because you are not checking for it in the parent branch. If you go to Automation > Templates you will find a rule called "When all sub-tasks are done → move parent to done" and as you can see it includes…

Default JQL cannot do a nested query like that, you would need to get an app like JQL Tricks or Enhanced search or any of the other apps in the Marketplace that extends JQL.

The error indicate that your AQL is not configured the right way, what does it look like? Based on the info you provided above the AQL would look something like this: objectType = LAPTOP AND "Serial Number" LIKE (<enter the number here>) Where are you getting the serial number from? Is that on the request form? If you for…

Here's an example that gets approvers from our Peoples schema. All you have to do is a lookup object and then use that to get the attributes you are looking for.

Hi @Piotr Mańkowski, Welcome to Atlassian Community! Yes, it is possible to copy attributes from an object to a custom field if needed. But you could also use the assets field, which Komputer is, and configure it to show more data then just the name of the object.

@Sue Lund in out-of-the-box Jira that is just the way it is, you would need to either add the form after the clone is created or use an app like Deep Clone for Jira.

Hi @[deleted], Welcome to Atlassian Community! Currently that is not possible, but Atlassian is working on a change that will open external links in a new tab, see JRACLOUD-9380 for more information.

There are examples in the documentation that shows you how to compare dates that you can find here.

You can do this with automation, a scheduled rule that runs a JQL that returns all defects that are unsolved. The rule would compare the created date against now() to see if it has passed the number of days and if so notify either via email/Slack/Teams that the SLA has been breached.

Once a field has been created you cannot change the field type, so you would have to create a new field.

Since the second automation is triggered by the first one you have to go to Rule details and check Allow rule trigger for it to work.

In it's simplest form the automation would look something like this: Note that you should encode64 the credentials in the webhook and/or make it hidden once you verified that it is working.