Alexey Matveev Expert

Hello, Parallel sprints are not available in next-gen projects only in classic Jira Software boards.

Hello, If you want to import and export only configuration, you should use such plugins as Project Configurator or Configuration manager.

You are most welcome!

Hello, You need to install the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview

Hello, You should convert your sub-tasks to tasks first and then do migration.

Hello, Open any filter, which you have. Then in the url change the filterId to your id (123456)

Here is the link: https://confluence.atlassian.com/jirasoftwarecloud/migrate-between-next-gen-and-classic-projects-957974933.html

Hello, You can not change workflow in the next-gen project. You need to add or delete the required column on the board. If you want to change a next-gen project to a classic project, You need to create a new classic project and migrate all issues from the next-gen project to the classic project.

@Ian Johnsen As I wrote in my previous post. Do not use roles in the project permission schemes. Use groups.

You are most welcome!

Hello, It means somebody else works with your issues on another board.

Hello, You should be the owner of the filter to modify it.

Hello, My changes were visible on the next day, after I made changes to my name.

Hello, the Rank is a global field. It does not belong to a board. If you change it on one board, then it will be changed on the other board as well.

Hello, You need to add the time tracking field to the edit screen and set the Original Estimate value, not Story Points.

Hello, You can use the bulk edit functionality: https://confluence.atlassian.com/jiracoreserver073/editing-multiple-issues-at-the-same-time-861257342.html Go to the transition multiple issues part.

@elisabethesbjornsson Good to hear!

@Katya Godneva You are most welcome!

Hello, 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 use the following JQL expression for your queue key in silJQLExpression('matchEnd(getUser(reporter).email,"@admin.com") > 0', '')

Hello, Maybe you could write a JQL query like this: not (status changed after -2d) AND status = "Internal Test"

Hello, You would need a plugin for it. You can have a look at the Structure plugin: https://marketplace.atlassian.com/apps/34717/structure-for-jira-projects-at-scale?hosting=server&tab=overview

Hello, You can not do it out of the box. You should use a plugin like JETI: https://marketplace.atlassian.com/apps/4977/email-this-issue?hosting=cloud&tab=overview

Hello, You would need an add-on for it. You could use also the Power Custom Fields add-on: https://marketplace.atlassian.com/apps/1210749/power-custom-fields-premium?hosting=server&tab=overview You could create a new SIL custom field with a code like this: return #{Closed Date} - created;

I am not sure if it is a permanent thing or not. But right now it is like this :)

Hello, You can not forbid project admins to add people to roles. If you do not want project admins to manage permissions, then do not use roles in the project permission scheme. Use groups instead. But it is not considered to be the best practice.

Hello, In the new Issue view (I think you are referring to this one), you can not change placement of fields

Hello, You can not do it out of the box. 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 create an edit screen with all fields for managers and developers. Then you…

Hello, You can use Service Desk automation to change the end date of a task. But it must be an event (an update event to the issue for example). Currently there is no way to make a recurrent task. But you could use an add-on. For example you could use the Power Scripts add-on:…

Hello, You should add user, groups or roles (roles preferable) to the project notification scheme. In this case users will get notifications only if they are defined to the event.

Hello, You can not do it out of the box. You would need an add-on for it. For example you could do it with the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could create a validator with a code like this: if (length(description) < 20)…