Mikael Sandberg Community Champion

If you belong to one of those groups listed you have the right permission, the next thing is to add you to the access list for each of the projects. This is done from Project settings > Access in each project.

Okay, then you are using next-gen projects and they do not have a permission scheme. I assume you want to do a bulk move, and in order to do that you have to enable the make bulk changes global permission. You can do that by: * Go to Settings > System > Global permissions * Ensure the user group you are part of has the…

Have a look at Manage project permissions and here you can find details about each permission.

There should be a move permission too, and you need that permission in the project you are moving the ticket from. The move permission should be just under Modify reporter in the Issue permission section.

Just because you have admin permissions in the target project does not automatically give you create issue permissions. You have to check the permission scheme used and make sure that you either belong to the role that gives you create permission, or add administrators to that permission. Have a look at How do Jira…

Hi @Xia Willuhn, Welcome to Atlassian Community! In order to be able to move an issue you need to have the create issue permission in the project you are moving the issue to. To do that, go the other project and check the permission scheme to find out what permission you need, by default you need to be part of the…

Natively in Jira you cannot have multiple portals on a single instance. But you could do it if you use an app like Refined for Jira Cloud or as you mentioned by having separate instances.

You can also add the epic from within the story, just click on the dot menu and select Add parent.

Hi @Nishant ClipyCam, Welcome to Atlassian Community! You are using a next-gen project and in order to link a story to an epic you have to create the story from within the epic, not from the create button.

The short answer is that you cannot do that. The field configuration just defines if fields should be shown or not and if they are required. The scheme only associate the configuration with issue types. In order to have a dynamic screen that changes based on what the user pick you would need an app like ProForma.

Okay, that is what my testing shows as well. I guess I could run a script on a schedule to see if approvals are still pending. Thanks for checking @Angélica Luz!

Hi @Daniel Jimenez, Welcome to Atlassian Community! One way of doing it is to use the incoming mail handler in Jira to create the tasks for you. Take a look at Create issues and comments from email for more information. 

Hi @Steve Rubin, Welcome to Atlassian Community! This is what I would do instead of having to create all those 500 users and the need to have a subscription that covers them too. I would create a custom text field and import the user to that field. This way you have a reference to the users, but you do not have to create…

One way of doing it is to use an automation rule, I would use a scheduled one because you manually trigger that one, that copies the value from your text field over to the new numeric field.

Thanks @Angélica Luz I suspected that. I assume that when someone approves it triggers a edit event, correct? If so then I should be able to work around it by trigger a web request and use tray.io to get the pending approvers and return that to Jira via an incoming web hook that update a field on the ticket.

Hi @Andrew Bishop, Welcome to Atlassian Community! You can generate a generic name for the ticket, the form allows you to hide fields, like summary, and give it a default name. But it also relies on request types, so you could have a request type for password reset, and then use the summary field to ask the customer which…

Does the user have access/license to JSM? Any user that you want to assign tickets to in a JSM project has to be an agent.

No, next-gen projects are limited to the three project roles that are defined. You can only add more roles in a classic project.

Yes, just go to admin.atlassian.com, under Manage subscription you can change the plan you are on.

If you have Scriptrunner this query should return the list: issueFunction in linkedIssuesOf("issuetype in (risks, blockers)")

Native JQL does not allow you to do nested queries, like show me all models and linked issues to those. You would need an app like Scriptrunner or JQL tricks, I have used both of these apps in the past to get a similar list. If you search the Marketplace there might be other apps that can also provide you with that…

Jira Cloud does not have an option to generate the support zip, that is only available on Server/Data Center. Instead you can grant support access to your site when you log a ticket.

I think your only option would be to use the REST API to do it in bulk, Create component. 

Hi @Barbara Nie, Welcome to Atlassian Community! There is no option in Git for locking a tag, and you cannot prevent someone from editing the tag locally. What you could to is add a hook that prevent them from pushing any tag updates to the remote repository. Have a look at this Stack Overflow question for some ideas on…

Yes, you are correct, the default permission scheme basically allows anyone with access to your instance to do almost everything. And changing it to limit what can be done does require planning. To make it easier I would start by limiting who can create new projects, and for existing projects either change the default…

You could use components, see it as a way of sub categorize your project. The template populates the components as an example, but you can always change that. We use components to categorize our tickets, and it can be anything from access requests to peripheral requests.

I am using Tray.io in order to populate Insight with records from Jamf, and the way I solved the Atlassian user ID was to first lookup the user in Jira by search in their email address. The returning object contains the account ID and I am then using it to populate the owner in Insight.

Hi @Juan Mateo Romero Rubiano, Welcome to Atlassian Community! Yes, you should be able to do this with automation. You could do this by using one of the Automation condition.

The reason they where moved to the backlog is that your new status(s) have not been linked to your columns on the board. You have to go into board settings and link the status to the right column, that should fix it.

Hi @Mirina Meppel, Welcome to Atlassian Community! Jira Service Desk (JSD) is the old name before Atlassian renamed it to Jira Service Management (JSM).