Alexey Matveev Expert

Hello, In Service desk you should set the Assignable user project permission correctly and the user, who will be assigned, must be a service desk agent.

You can change the current workflow. Create a transition from any status to itself. When you change a priority, the status will not be changed. When you push the ... button and choose the created transition a new dialog will be opened.

Hello, If you are on Jira Server, then have a look at this guide: https://developer.atlassian.com/server/jira/platform/creating-a-custom-release-notes-template-containing-release-comments/

I see. You can either ask your Jira Administrator or delete the status and create a new one.

Hello, It means that you are on Jira Cloud and you created a next-gen project. You should create a classic project.

Hello, 1) To migrate these 3 plugins to jira cloud, do they need to be fully rebuilt? If you did not build the plugins with Cloud in mind, then the plugins should be rebuilt 2) Can plugins continue to use the Postgresql database that they use today? Will a postgresql database be created by the cloud platform? it's…

Statuses are Jira level settings. You need to be a Jira admin. Go to cog wheel -> Issues -> Statuses

It is not a project setting. It is a Jira setting. You need to be a Jira Adminisrator. Are you on Cloud or Server?

Hello, It will affect all projects, which use the same workflow scheme.

Hello, Go to Issues -> Statuses, find the required status and push the edit button.

I have not met such a message before.

Hello, Are you using some kind of an app? If so, you should provide the name of the app. I can not figure out how you migrated a project.

It must be Data Center, not Server.

Hello, This option is only available for Jira Software or Jira Service Desk Data Center. It is not available for Server

I have not found public rest api to add a field to a screen. You can try to find web calls, which are made to Jira Cloud and imitate them. If you want to see yourself all available Rest Api methods, you can find them here: https://developer.atlassian.com/cloud/jira/platform/rest/v3/

Hello, You need generate a token for each Jira Server. If you have a staging server and a production server, then you need to generate a token for the staging server and a token for the production server.

Hello, You need to add the field to the create screen for the issue type, an issue of which you are trying to create. To add a custom field to a screen ,go to the Project Settings -> Screens. Find the Create screen for the required issue type and add the custom field.

The custom field should be a user or group type.

Hello, You can use custom fields of user and group types in the permission schemes. That is why you do not need security levels. Go to project settings -> permissions. Find the browse project permissions and set your custom field there.

Hello, To see it better, you would need a plugin like Big Picture or Structure Gant.

Hello, Have a look at the Ceptah Bridge plugin: https://marketplace.atlassian.com/apps/9203/ceptah-bridge-jira-ms-project-plugin?hosting=cloud&tab=overview I am not sure what you mean by sub-task level 3. If you mean that the first level is an epic, the second is a task and the third is a sub-task, then it is possible.

I believe that you are talking about Jira Cloud. You can change the New Issue View to the old Issue view, if you go to your profile and disable the Lab feature: https://yourdomain.atlassian.net/secure/ViewPersonalSettings.jspa

If you want to get a value of a field on a screen, then you should use the argv list to do it. It would be like this: argv["customfield_15800"] If you type customfield_15800, it takes a value saved in the Jira database, which is not what you want.

Hello, Your OnChangeCustomfield.sil should look like this: switch(argv["customfield_15800"]){ case "Normal Change": lfShow("customfield_15900"); lfShow("customfield_15901"); lfHide("customfield_15904"); break; case "Emergency Change": lfHide("customfield_15900"); lfHide("customfield_15901"); lfShow("customfield_15904");…

You take a classic project for a new next-gen project.

Hello, There is no field level permissions in Jira. You can not do it. The only thing is to put all fields, which must be editable by a specific role, to a transition, not to the Edit screen, and then add conditions to the transition.

Hello, You need to have the manage sprint permission in all projects, from which issues are selected or limit the selection of issues to the project, where you have the manage sprint permission. You can do it by changing the filter for the board (board settings -> general)

Hello, I believe that you created a classic project, not a next-gen project. If you want to make your next-gen project to be classic, then kindly read this article: https://confluence.atlassian.com/jirasoftwarecloud/migrate-between-next-gen-and-classic-projects-957974933.html

And did you restore the backup of the old site before you restored attachments?

Hello, There can be multiple site-administrators, but they will all have the billing option.