Alexey Matveev Expert

Hello, You can not migrate a classic board to a next-gen board. You can only move issues from a classic project to a next-gen project and begin to use the next-gen board. Right now the next-gen projects are under active development. Next-gen projects lack many feature from classic projects. Before migration kindly make…

Hello, Kindly have a look at this thread. https://community.atlassian.com/t5/Jira-questions/Jira-unable-to-access-on-port-80/qaq-p/33337

Hello, Go to project settings -> permissions and grant the browse projects permission to reporter. Beside the reporter, leave there only groups, roles and users, who must see all tickets in this project.

Hello, There is no permission like this out of the box. You could remove the required custom field from the edit screen and create a transition with a screen, which contains the required custom fields. You could add the User In Project Role condition to this transition to let only users in the Project Administrator role to…

Hello, Go to cog wheel -> system -> project import. You ca find more info here: https://confluence.atlassian.com/adminjiraserver/restoring-a-project-from-backup-938847691.html

Hello, It is not possible. You must provide a value to make a field visible on the view page.

Hello, I guess, you JQL query must be like this: status = Resolved and status changed to Resolved before -3d

Hello, You should not unzip the MigrateToMySQL.zip file. Just write MigrateToMySQL.zip during import.

You would need an add-on for it. For example, Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could write a script like this: jql =<span> </span>"project = ProjectKey"; string[] issues = selectIssues(jql);for(string iss in issues) {…

There is no way to do it via UI. The best way to use Jira API to copy values from the old field to the new one.

Hello, Have a look at the two Dimensional Filter Statistics gadget: https://confluence.atlassian.com/jira064/adding-the-two-dimensional-filter-statistics-gadget-720416991.html

Hello, Kindly read this KB on how to migrate Jira Server to Cloud https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html Kindly read this KB on how to migrate Bitbucket Server to Cloud:…

Is this field type from a plugin? Anyway, you should create a new field and then copy all data from the old field to the new one.

Hello, If you are on Cloud, then there is the Field Required validator. If you are on Server, you would need an add-on. 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 add a validator with the…

Hello, What do you mean by "project specific single select"? If you want to have different options for different projects, then you should create a field context for this project. You can find more info here:…

Here it is https://yourdomain.atlassian.net/secure/admin/GlobalPermissions!default.jspa

You can find more info here: https://confluence.atlassian.com/servicedeskcloud/adding-request-participants-732528959.html

Choose Jira in the screenshot: Then Jira settings -> Global permissions

Hello, It is a next-gen project. You can categorize it yet. If need to set a category for a project, you should create a classic project.

Hello, Go to Issues -> Statuses. Find the Approved status, click edit and change the Category field to To Do:

It is not possible.

That is right. When you create an issue the default value is taken for the project. 

You can not use the currentUser() with the approver function.

Hello, You would need an add-on 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 add a post function with a script like this: #{user field name} = projectPM(project); You can read more about…

Hello, You can go to project settings -> permissions. If this permission scheme is used by other projects, copy the current permission scheme and associate the copied scheme to the project. Then revoke all users, role and groups from permissions.

Ok. Now I understand. You created a next-gen project. This type of projects do not have subtasks yet. But it is on the Roadmap. And subtasks will be available in a future release. If you need subtasks right now, then you should create a classic project.

Hello, Go to project settings -> issue types. Then choose Actions -> Edit Issue Types and add a sub-task issue type to your issue type scheme.

Hello, Go to the project settings -> permissions and grant the Browse projects permission to Assignee and delete groups or roles, to which subcontractors are included.

You are welcome!

Hello, Go to the project settings -> permissions and have a look at the Transition issues permission. I guess only Assignee is defined there.