Mikael Sandberg Community Champion

Hi @Klodian Lulaj, Welcome to Atlassian Community! What you see is expected, the Request Participants field is only available on the portal as the Shared with or in the issue detailed view and cannot be added to a form.

Hi @Friskybadger, Welcome to Atlassian Community! This can be done by configuring the permission scheme and setting up issue security. Your customer has to update all the permission schemes that they have so you only have access to the specific project, and if you should only have access to specific issues then also add…

Hi @Ramazan Bıyık. Welcome to Atlassian Community! In order to add/edit/delete options to the field, go to Settings > Issues > Custom fields. Locate the field and then click on the three-dot menu on the right and select Context and default value. From here click Edit options and you can modify the values. 

Hi @Lee Beardshaw, Welcome to Atlassian Community! On the Cloud products the way you create users is to invite them to the instance and entering their email, there is no other way to create a user. The Create button only exist on the Data Center side.

@Melanie Beaudry Desjardins @Tracy Gilmour you do this by creating a new issue type screen scheme, were you can define the screen scheme that each issue type is using, something like this:

Are you updating the issue in the same automation that is sending the notification? If so, add a re-fetch issue data action in order to make those changes available to the automation.

No, services are shared across all JSM projects. Once the services object schema in Insight (soon to be Assets) has been opened up you can hopefully specify which project it should be visible in, at least that is what I suggested to the product team when I talked to them about it.

Hi @TLBrewer, Welcome to Atlassian Community! The short answer is no, you cannot make the form just send an email without creating a request. What you could do is to use automation that sends the email when the request is created, and then close the request. 

The app for Zendesk allows you to restrict the projects that are available on the Zendesk side, and that will remove the Zendesk comment tab if the project is restricted, but it will not remove the Zendesk Support field.

Correct, SFDC Comments cannot be removed But the one for Zendesk you should be able to remove, I think I saw a setting for it (I cannot get to the configuration screen for Zendesk at the moment to confirm).

Hi @Donald Wheeler, Welcome to Atlassian Community! I assume you are talking about the two fields that are shown in the right panel in the issue view. Unfortunately you cannot remove those, the visibility is controlled by the corresponding app, and the majority of apps does not allow you to configure it those fields should…

What you see is expected behavior and it has to do with Customer permissions and issue level security. When you use the Create button none of these are set yet, and therefor the request participants field is not visible. Customers can only add participants from the portal or via email, and JSM agents can add participants…

What you are looking for are instances were sprint if empty, so this query should do it: sprint is EMPTY

You would need an app in order to get external data to feed into a Jira field, like Elements Connect or External Data for Jira Fields. I would suggest that you search the Marketplace for external data and check out the apps.

Does the under review status have the approval process enabled on it so that an approver can either approve or deny the request? If not that is the reason your automation is not working, since the Approval completed is tied to that process. Based on what you are describing your approvals happens in the subtask and once…

Turns out this is a bug, JSDCLOUD-11142 - Looking up Insight objects in automation when the IQL contains an & throws an error and returns no results 

Hi @Manny Singh, Welcome to Atlassian Community! Is one of the projects selected by the filter a team-managed project? That would explain why you have two To Do statuses, and then both of those has to be mapped to your To Do column. Team-managed project are sort of its own island and cannot reuse status names for example…

Hi @Liz Ralph, Welcome to Atlassian Community! Yes, you can use bulk change to do this. Just filter out the issues you want to change and then click on the three dot menu up in the right-hand corner and select Bulk change and follow the on screen instructions.

Happy Jira Admin Appreciation Day!

Here's my LinkedIn post. 

Take a look at Configure advanced issue workflows, you have to go to the workflow and add the post function to the transition that takes you to the escalated status. 

And if you want to transition the request into another project you can do that with automation by copying the issue over to the other project and close out the original one.

You could do this using post function and a custom field. The way I do it is that I have two transitions, one for Tier II and a second one for Tier III, and when you escalate to either one, there is a post function that sets the field to corresponding tier. Then on the queue you just have to filter out the custom field to…

Escaping it doesn't work either unfortunately, the error message is the same and it cuts off the query after finance. It looks like it might be a bug in the lookup. I have a workaround by using a Dispatcher automation that sends a web request to the automation that does the actual work based on department, and in the case…

Not without an app, if you want an e-signature your only option is Speedy PDF Sign-Offs For Jira Cloud. What the Approve/Decline using the approval will do is add a comment in the history of the issue who approved/declined it. 

You can turn on so that they get two buttons in the email to either approve or decline Just go into the customer notification for approvals and there is a checkbox to enable this.

You could use the approval process to this this, that would allow them to either approve or decline the task. 

You are absolutely correct.

Hi @Samir Koirala, Welcome to Atlassian Community! When you are searching for specific labels you also have to include when labels is empty for it to work. So in this case your query should look like this: project = DEVOPS AND (labels not in (TST, PRD) OR labels is EMPTY)

Under rule details, have you checked the box that allow the second automation to be triggered by other automations?