Mikael Sandberg Community Champion

Hi @[deleted], Welcome to Atlassian Community! How are you triggering the automation? Also on the comment action, have you disabled/unchecked this one?

Hi @Niyati Joshi DISH, Welcome to Atlassian Community! You would have to contact your IT to get help with this, the majority here on the community are Atlassian customers/partners and do not have access to other companies Atlassian instances. 

Yes this is possible. If you look in the library there is an automation for this called Resolve issues due to inactivity that you can use

Hi @Jacob Morris, Welcome to Atlassian Community! The out-of-the-box Dashboard does not have a gadget that will show you this information, the closest is the Jira Road Map that will show it based on the project, not individual epics. You may want to checkout the Marketplace to see if there are any apps that will do it for…

You are sharing the filter with users that have access to the projects, but you also have to change the JQL part too, currently it is set to: project = APM ORDER BY Rank ASC That needs to change to something like this: project in (APM, "APM Software Test Project") ORDER BY Rank ASC

Okay, what controls what you see on the board is the filter, and currently it is only selecting one project. So if you want to see issues from more projects you have to update the filter.

You cannot set the request type using the edit issue action, you have to use the Edit request type action in order to do it.

You should be able to select if the project is a team-managed or company-managed project after you have selected which template to use if you are on the new create project experience. If you are still on the old experience you can switch between team-managed and company-managed by clicking the button under the templates.

Go to project settings > Fields and click on the pen at the top. This will take to the field scheme, from here find the paragraph fields click Renderer and make sure that the renderer is set to Wiki Style Renderer.

You are correct, the reason the "Issues in this Epic" is not showing up is because you are using the epic in a JSM project. It would only show up if you link an issue to the Epic.

Go to admin.atlassian.com and look up the user. Make sure that the slider has been enabled for Jira Software.

I have multiple automations because we are using tray.io to do some of the automation like getting the manager and notify them and the system owner via Slack and add the user to the right Okta group. We store the application information in Insight, so the automation to get the system owner looks like this:

Hi @Andrea Georgi, Welcome to Atlassian community! Check and make sure that the user has a JSW license. 

Hi @Gabriel Freddi de Matos Santos, Welcome to Atlassian Community! In order to mention someone you need to know their username or ID in Slack. Have a look at this article describing how to get that added as properties so you can mention them, Mention someone directly in Slack via Jira Automation

Hi @Cody Powell, Welcome to Atlassian Community! You can do this using automation and the approval process in JSM. This is how we do it for our automated application requests. The first approval has to be by the manager, and once approved it goes to the system owner(s) for approval. So you could do something similar where…

Hi @Horst Neyer, Welcome to Atlassian Community! There is currently an active incident regarding the Trello app, see https://trello.status.atlassian.com/.

No, an issue type can only be associated with a single workflow. If you need to use a different workflow you have to use a different issue type.

The post function would be on the transition that takes you to Ready for QA, click on the arrow that takes you to the status and you should see it.

Hi @Richard Rivera, Welcome to Atlassian Community! You may want to check your workflow to make sure the assignee is not set as part of the post function when moving it to Ready for QA. 

You would need an app like Issue Matrix in order to do that. The out-of-the-box Jira does not allow you to add more columns to that view.

Correct!

My bad, I missed the part about single project. In that case you would have look for an app like Elements Connect and setup a dependency to the issue type field, not sure if it works on the JSM portal or not.

Hi @Scott Federman, Welcome to Atlassian Community! You could do this by setting up a custom field context for each issue type, that way you can control what values are available for each issue type.

Hi @Sydney Siegmeister, Welcome to Atlassian Community! JSM includes Atlassian Assist, in which you can turn on Two-way creation, meaning that any issues create in JSM will create it in Assist (Halp) and the customer will be notified in Slack.

Like @Coltin Rose mentioned, if you have Okta then look at creating an Okta workflow that when you add a new user it trigger the workflow to also import it in Insight via REST API. 

@Pierrick Welcome to Atlassian Community! Team-managed projects does not have a permission scheme that you can change.

Hi @RR, Welcome to Atlassian Community! Paragraph fields are using Wiki Renderer notation, so in order to create the link with an alias you would do it like this: [Atlassian|https://www.atlassian.com] That would give you a link like this Atlassian. You would also have to change the renderer used in the project. Go to…

Yes, that is possible. You can either move each issue over to the new project, or you can create a filter that gives you all the issues you want to move and then use the bulk change option to move all issues.

You would need an app in order to do field security, Jira out-of-the-box does not support that, unless you add the fields to a transition screen and only allow specific groups to use that transition.

Yes, that's possible.