Mikael Sandberg Community Champion

You have to click on the actual transition, not the status in order to see it. So in this example I want to make Mark as Done transition available since that will move the request to Done. So I click on the transition and it will then show the option you are looking for.

Hi @Harshil Shah, Welcome to Atlassian Community! In order to allow customers to move the request to a specific status you have to go into your workflow and enable customer transition. Old editor: New editor:

ProForma forms is no longer available as an app in Cloud, it is now part of JSM. The only way you can get access to Advanced Forms (ProForma Forms) outside of JSM is if you had the app installed before it became a feature in JSM.

Hi @rnaray43, Welcome to Atlassian Community! It is possible, but you need an app that allows you to create custom fields that are being populated by external data. If you search the Marketplace there are a handful of apps that can do this. I have used Elements Connect in the past to get data from an external database, but…

Check out this article that outlines how you can import the request type during bulk import. Basically what you need to do is find the portal key and the request type key and map that to the request type field and also set the issue type. I have used this to bulk import request types and once you have all the data it is…

In out-of-the-box Jira it is not possible to do this, you would need an app that allows you to set field security. If you search the Marketplace there are apps that can do this.

You can restrict what that user will see by setting up issue security and then use automation to set the level based on the request type. Basically what you need to do is create an issue security scheme, I would recommend one for IT only and one that includes the tech. For the existing issues you can use bulk edit to set…

Based on this KB it looks like you have to be a member of the team before you can make changes unless you are a org admin.

There is a way of manage who can be added, if you click on the three dot menu and select Team settings there is a checkbox to allow anyone to be added. There is also a delete option under the three dot menu. Regarding disable that is not currently possible, you can only delete.

Besides using it for asset management we use it for application access approvals, the object has the system owner and the group that the user should be added to when the request gets approved. In HR it is used for the approval process that we have for employee change/transfer, there is an object for each department with…

This should probably be its own question. Are you talking about Forms or the request form? The request form is project specific and cannot be used across projects.

It is possible, it all depends on how you determine how many sub-tasks are needed. Does the issue has a field on it that controls that?

You can use the substring smart values to get the specific text if the description in the epic always have the same before and/or after text, something like this: {{issue.description.substringAfter("Some text ")}}

The short answer is no, there isn't a setting that would allow you to automatically add a group as default, this has to be manually done. 

This is what the automation looks like for the reminder: The due date is set as part of a post function when the request is moved to approved status.

Just to add, the number of licenses for the app has to correspond to the number of licenses that you have for your Atlassian product. You can read more about it here in this FAQ.

It is possible, but you would need an app like JQL Tricks, Enhanced search or any of the other apps in the Marketplace that extends JQL so that you can do nested queries like the one you are trying to do.

Hi @Mike Duncan, Welcome to Atlassian Community! I have a similar automation that sends our a reminder 90 days before renewal needs to be done. The way I am doing it is that when the original request gets approved a due date is set on it based on the contract length. The reminder automation is running on a schedule and…

Hi @Moon, You can only hide fields from the request form if you are using a Company-managed project, it cannot be done in a team-managed one.

Hi @Evelyn Hulsey, This has changed since last year, now you have to configure the SLA that you want to hide in order to remove the SLA field. If the request does not have a related SLA the field will not be shown. 

You can't make request types available for just a subset of users/customers. The only way around that would be to use a separate project that those specific users have access to.

As you have discovered there is no way of restricting specific request types from being accessed from the portal. So your approach using two different projects would be the way to go. You can control who have access to the project by updating the customer permissions. For the one you want to restrict, set the channel…

Hi @Tomas Fernandez, Welcome to Atlassian Community! You could do this by creating a customer organization for HR and add the HR members to it, and then configure the project to share requests with the organization. Please have a look at Group customers into organizations for more information. 

Hi @Claudia Ospino, Welcome to Atlassian Community! Atlassian Intelligence is only available if you are on Premium or Enterprise plan, If you participated in the beta and are on the Free or Standard plan it will be deactivated on June 30th 2024 unless you upgrade your plan as outlined in this KB. The second screenshot,…

Hi @Rashida Garner, Welcome to Atlassian Community! This would be a question for your Atlassian admin. Most of us here on the community are customers and do not have access to other customers instances. 

Here is an example of how I do it for off-boarding requests, this one is creating a task for a team in their project with the information that they need:

This can be done with automation and smart values. To post multiple smart values in the description fields you just have to list them, something like this: {{issue.summary}} {{issue.mycustomfield1}} {{issue.mycustomfield2}}

Most of this you could get via the Dashboards API, but getting the data and content would make it hard, since the API that gets the gadget will not give you the underlying filter.

That is a global permission that allows users to create team-managed projects. If you go to Settings > Systems > Global permissions you can either change who can do this or remove that option completely. As a Jira admin you will be able to create TMPs even if the permission is removed.

Forms do not have any smart values yet. But you can get data out of the form by using the Forms API if you need to and do not want to link the Forms fields to Jira fields.