Mikael Sandberg Community Champion

I suspect that there is some type of hidden code in the email that the email handler cannot interpret and that is why you see it in the request. I would check the raw email, you can get that by going to Project settings > Email requests > View log. From here located the request and download the raw email.

Okay, so team managed projects can only have a single sub-task, you cannot create new ones in it. The screen shot above is showing issue types available for company managed projects, and those cannot be used in a team managed one.

Hi @Lenin Falconi, Welcome to Atlassian Community! You can only have one column that can create new issues, each column is tied to one or more statuses in a workflow and it is only the initial status that the create transition can be linked to, it cannot be linked to multiple statuses.

Hi @Totore Ideatore, Welcome to Atlassian Community! Are you using a company managed project or team managed project? If it is a company managed project you have to update the issue type scheme that the project is using before the new issue type will be available.

@Marc Isikoff You cannot set the trigger issue's assignee in a branch, you can only edit the branch issue. I would break that part out so you have two automations. The first one would do a web request to the second automation with the key to the trigger issue and the assignee that you want to set.

You can find the best practices regarding resolution here. Resolution is a way to indicate that the issue is resolved and that is how Jira knows where in the lifecycle the issue is. The status is just that, it indicate where in the workflow the issue is. Lets say you move the issue to Done, then the resolution indicate why…

So it sounds like your workflow is requiring something to be entered or you need to be in the right group/role. If you can share your workflow it would be easier to tell what is going on.

The easiest to find the Id for your project is to go to the portal, the Id is part of the URL: servicedesk/customer/portal/1 That is the Id that you can use with the JSM endpoint to create new request types. And if you are looking for the request type Id you can get that from the portal as well by going to the request type…

It all depends on what the original email looks like, my guess is that there is something in it that the email handler cannot convert. So an option would be to remove that line via automation and smart value that removes that part of the description.

The default Jira can only block the transition if you have enabled the condition Sub-task Block condition. If you want to do it based on linked issues you would need an app like Scriptrunner which extends the conditions that you can add. There are other apps in the Marketplace that can do this so have a look there and see…

Hi @Lloyd Francis, Welcome to Atlassian Community! It all depends on how your workflow is configured if you have a Closed status or another status that indicate that the task is done. In the issue view you should see different workflow status up on the right hand side that the task can move to. In Jira Cloud that is a…

If those stakeholders have access/accounts on your instance then the user picker field will work. If the stakeholders are external with no access to your instance then you would have to use a text field that you can enter their emails in, and then the automation can parse those out.

You said you had a similar automation for bugs that works, correct? And are both bugs and stories using the same workflow? Does the global transition to Blocker have any conditions on it?

Hi @Kehinde Odebo - QPBAB, Welcome to Atlassian Community! The reporter field is a single user picker field so you cannot add multiple users to it. What you can do is create a new custom field for stakeholders that is a multi select user field, you can then use that to notify your stakeholders either by automation or…

What does your workflow looks like? When are you setting the resolution? Normally the resolution is set as part of a transition since that field becomes required when it is added to a screen.

It all depends on how you want them to submit requests to your project. If you only add them to the Users role they would not have access to the portal and would only be able to submit requests by clicking the Create button. Now that might be okay since Atlassian now allows you to use the request type fields, but when I…

@Karie Kelly It all depends on how you have your permission scheme set up. @Joseph Chung Yin is correct, if you want your JSW users that do not have a JSM license to be able to add internal comments they can be added to the Service Desk Team role, or as in my cause I have that separated out so JSW users that need to add…

Hi @Karie Kelly, Welcome to Atlassian Community! Jira Software users that do not have been assigned a JSM license are considered to customers if you add them to the Service Desk Customer role in the JSM project. All customers are free in JSM, you are only paying for the agents. You can also add your JSW users to the Users…

The short answer is no, you cannot restrict the request types on the portal via groups.

It can be done using automation. You would have to turn off the customer notifications like Public comment added, Customer-visible status change and Request created and then set up the automation so it notifies all customers involved on the request after it has been approved.

No that is not possible, and my guess is that epic name may be removed in the future.

Hi @Mercker, Jeramie, Welcome to Atlassian Community! Yes that is possible and you can do it using issue security and automation. Have a look at this KB for more information on how to set it up. Basically you create an issue security scheme and once added to the project you can create an automation that monitors your…

Hi @Nataliya Eltsova, Welcome to Atlassian Community! What you see is expected, Atlassian announce earlier this year that Epic name will become a optional field and Summary will be what you see when linking issues to it. You can see the announcement here. 

Hi @Dylan Allison, Welcome to Atlassian Community! You have a couple of options. You can use Custom charts for Jira and the simple query gadget to prompt the user to fill out parts of the query. I bet there are other apps in the Marketplace that can do this as well. The other option would be Atlassian Analytics that is…

Yes, you can "turn off" or change who can create team-managed projects by updating the global permission that allows you to create TMPs.

If you go to the generic link for the form and then fill out the project, issue type and form you will see a info box that has the link with those values already filled out.

Yes, your filter should looks something like this: issuekey IN updatedBy("<your name>", "-1h") This would give you the issues that was updated by you within the past hour. Once you have the filter then you can do the bulk change on those.

Yes, Proforma Forms are now part of JSM. You can learn more about it here.

Hi @Zoltan Nyiri, Welcome to Atlassian Community! The community do not have access to customers instances, so you need to contact your admin in order to get access. You should be able to request access to the page directly within Confluence, that will trigger an email to be sent to your admin. 

You have a couple of options. JSM has reports that allow you to create one that shows you SLAs met vs breached over a period of time. There are also apps that can do this for you, we are using Custom charts for Jira to create dashboards that shows us met vs breached SLAs, but you could do the same thing with the other…