Alexey Matveev Expert

Jira will map old statuses to new status for Jira issues. It will not change any filters or boards. You need handle them manually after migrating all issues to the new workflow

Hello, You should go to project settings -> fields and make original estimate and remaining estimate fields as optional.

Hello, A project admin can edit workflows if the workflow is not shared. If you do not want this feature, then remove this user from the Extended Workflow Administration in the project permission scheme.

Hello, You should add this user as a participant to this issues.

You said that you have problems with unmapped statuses in a board. You should first handle the migration of issues to the new workflow. And later you should map statuses to column in the board

Hello, Add the Update Issue Field post function to the transition, leading to the Closed status, and set the resolution field there

You should map statuses in the board after you migrated to new workflow

Go to board settings -> Columns. You will see there unmapped statuses

Hello, I have not done any preliminary tasks before switching a workflow. If some issues must be migrated to new statuses. then you will be asked to provide new statuses for such issues. That is all.

Hello, You could use SIL for it. Create a live field with a code like this: if (isNotNull(parent)) { if (%parent%.issueType == "Task" && !isUserInRole(currentUser(), key, "Administrators")) { lfDisable("assignee"); } } lfEnable("assignee");

And if you try to map issue statuses?

I am not sure why, but I never needed to have a remaining estimate in story points. I guess it is a matter of methodology.

Hello, You can not delete active sprints. You need to complete this sprint first and then delete in the Sprint report.

Hello, You would need to create a new field and let users fill it up.

Hello, How do you send your Rest Request. I guess, the request is not encoded. You can read more about encoding here: https://www.w3schools.com/tags/ref_urlencode.asp

You can use the permission helper to find out why users do not have the browse projects permission. You can find more info about permission helper here: https://confluence.atlassian.com/adminjiracloud/using-the-permission-helper-868982879.html

Hello, Have a look at the dbconfig.xml in the jira_home directory and make sure it has the correct connection to the database.

Hello, To add a user to the Service Desk Team, you need to go to project settings -> users and roles and add required users to the Service Desk Team role.

Hello, You would need the Portfolio plugin: https://marketplace.atlassian.com/apps/1212136/portfolio-for-jira?hosting=cloud&tab=overview

Hello, It is not possible for the Story Points field.

You could use an add-on to create issues. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could write a post function to create multiple issues with this function:…

Is this user included to any group?

You should create multiple automation rules. Each rule would create one issue.

Hello, Go to the board and change the filter for this board (board settings -> general). This filter must also select issues from the required next-gen project.

Hello, Could you give more details on what the user can not add to any project? 

Hello, You can use the Jira Service Desk automation to create issues. You can find more info here: https://confluence.atlassian.com/servicedeskcloud/automating-your-service-desk-732528900.html

Hello, What is the type of the Cyclename field? If it is from a plugin, you should ask the developers of this plugins. Maybe they changed the search operand for this field.

Hello, It is not on the roadmap yet. You can see the roadmap here: https://www.atlassian.com/roadmap/jira-software?_ga=2.184994784.856277697.1543736872-65270402.1526147845

Hello, I think you would need a plugin for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could write a validator like this: if (issueType == "Epic" and currentUser() =="user1"){ return true; } return…

Hello, It should be "Epic Link" = "Epic1" OR "Epic Link" = "Epic2" OR "Epic Link"= "Epic3"