Mikael Sandberg Community Champion

Make sure that your workflow is clearing out the resolution field when you reopen an issue. If the resolution field is set then you will see the strike through because Jira is considering all issues that have a resolution to be completed.

In order to enable the rich text editor for your custom field you have to go and change the renderer used. Go to Project settings > Fields and click on the pencil to edit the field configuration. Next locate the field and click Renderers and select Wiki Style Renderer.

I just noted that the new cmd+k menu that is replacing the dot menu has Add flag and you can now add it to JSM requests. In order to see that a request has been flagged in the queue you have to add the field Flagged to the view.

One way of doing it would be to use either labels or components and then update the queue so that it shows either one of them. You could then identify requests that needs attention by looking for the label/component.

Hi @Thomas Scott Van Emburg, Welcome to Atlassian Community! Yes, you need permissions in both projects to Move Issues, Edit issues and Create Issues in order to move issues between projects. Once you have that then you can click on the three-dot menu up in the right-hand corner when viewing the issue and you should see…

Your rule should look something like this: In order to @ mention someone you have to use their Atlassian Id like this: [~accountId:{{assignee.accountId}}]

In order to disable the SLA for changes you have to go to Project settings > SLA and change your goals so that it does not cover changes. For example if you use "Ticket category" = "Service requests" in your goal that would not include changes, only request types that belongs to the Service request category.

Hi @Michael Adubasim, Welcome to Atlassian Community! What you have above should work, and if your JQL used in the scheduling step includes priority = High then you do not need the If component. What is failing? Is the @ mentioning? What does the JQL look like that you should have specified in the Scheduled step?

The flag feature is Jira software specific, there isn't a similar feature in JSM, unless you are using ITSM. There you can mark incidents as major incidents which will flag them like this:

Hi @Ellyot Rhee, Welcome to Atlassian Community! The default issue hierarchy in Jira is Epic - Story/Task - Subtask, and when you are adding a child issue it implies that you want to add a child issue to an epic. If you are on the Premium plan or higher you get access to set your own hierarchy above epics, but the default…

Hi @Owen_Pullam, Welcome to Atlassian Community! A rule like this should do it: You would have to add a condition before the send email so it only picks up the specific pages, as the example is set up it would pick up all pages that was last updated 3 months ago.

Hi @[deleted], Welcome to Atlassian Community! In order for an issue to show up in the calendar view you have to set both start date and due date. Have a look at this KB for more information. 

Out-of-the-box this is not possible to do. You would need an app from the Marketplace that would allow you to add more fields to the list view and sort on them.

Hi @Amgad Atef, Welcome to Atlassian Community! There is an active incident that is affecting editing workflows, please check https://jira-software.status.atlassian.com/ for more information. 

Hi @Thomas Carney, Welcome to Atlassian Community! The short answer is no, that is not possible. The only option would be to delete the project and start over. The real question is, why would you like to reset the numbering? Is it just esthetic? 

The underlying issue is that the mail handler in Jira is plain text, it tries to handle html, but especially when it comes to signatures it has issues with it. The only other option would be to add an external email service and hope that it handles signatures better.

Hi @korowa_ags, Welcome to Atlassian Community! If you go to Settings > Products > Email Requests you can enable Hide email signatures, and also add custom text that is should detect. This is not fool prof since not all signatures are the same, but it should help in the majority of the cases.

In the project go to Project settings > Customer permissions and make sure that Customer sharing is set to the second or third option so that customers can add new customers. Then go to Settings > Product and make sure that Email Requests is set up so anyone can create new accounts.

Hi @Alisa Collins, Welcome to Atlassian Community! No, team-managed project cannot set the view level on individual issues, you can only restrict who can view different issue types. In order to restrict issues to just the ones that they created, are assigned to or watching you have to use a company-managed project and…

If you are using a single user picker custom field you can limit it so you can only select users that belongs to a specific group. You could then use that as the field as the approver. All you would have to do is create a new group that only have the two approvers in it.

You would need an app from the Marketplace in order to do that. The built-in survey cannot be sent as a separate email.

Is Distinct Assignee a custom field? Or are you trying to show the assignee? If the latter then the smart value would be {{assignee.displayName}}. And in you are automation are you using a lookup issue component? The {{#lookupIssues}}{{/}} only works if you are using a lookup issue first.

@Julio Hernandez The only thing you need to define in the web request is the endpoint to get Okta user, and the API token key that has been set up in Okta. The Okta developer documentation should have all the information you need.

You are being redirected here to the Community when you click on contact support because you are on the free plan. The free plan only include support from Atlassian Community. If you add your question here then the community can help you out.

Hi @magendran.sukumaran, Welcome to Atlassian Community! You should contact your Confluence admin regarding this. This community is mainly made up of Atlassian customers and as such we do not have access to other customers instances. 

Hi @Fox Campbell, Welcome to Atlassian Community! {{worklog.comment}} should work. {{worklog.comments}} is not a smart value that can be used. And regarding you bonus question, the answer is no, there is no URL that would take you to the worklog tab.

Hi @Resmi Ravindran, Welcome to Atlassian Community! You have a couple of options. You can create an automation that tiggers on issue created that sends the email to the group. You other option is to create a group in Jira that has the same users in it and then add that group to the notification scheme the project is using…

Viewing an issue is not an event in Jira, and that is why you cannot trigger on it. Automation can only trigger on events like transition, field changes etc.

Hi @Josue Rodriguez, Welcome to Atlassian Community! What you see is expected, the security level field is added on the screen that the issue type associated with your request type is using. If you want to verify that the field is there, go to Project settings > Screens, select the screen scheme for the issue type in…

Hi @Fernando Brandao, Welcome to Atlassian Community! Correct, out-of-the-box JQL cannot do nested queries so that you can get the parent issue with its children, unless you specify the parent issue in your query. You would need an app from the Marketplace that extends JQL in order to do it. I have used JQL Tricks and…