Alexey Matveev Expert

Hello, I do not think that in the near future the next-gen projects will be mandatory. They currently lack lots of feature of classic projects.

You are welcome!

Hello, Go to project settings -> fields and make the DoR and Dod fields required. You can find more info about field configuration here: https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

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 write a condition like this: string[] keys = subtasks(key); for(string key in keys){ if (%key%.issueType == "required issue type" && %key%.status != "required…

Hello, Could you give more info what period you mean? A screenshot would be great.

You should create a board from a filter. You can find more info here: https://confluence.atlassian.com/jirasoftwarecloud/creating-a-board-764477949.html

Hello, To what admin options you do not have access?

Hello, What do you mean by global board? You can always create a board from Boards -> Manage all boards and provide a filter for this board.

Hello, You should copy the current workflow scheme, change this workflow there and associate the copied workflow scheme to the required project.

Hello, Project archiving is available for Jira Software Data Center and Jira Service Desk Data Center. You can find it here: https://confluence.atlassian.com/adminjiraserver/archiving-a-project-938847621.html

Hello, Have a look at this thread: https://community.atlassian.com/t5/Jira-Software-questions/In-the-next-gen-project-custom-fields-are-not-displayed-for/qaq-p/931696#M36076

You are welcome!

I do not think you can use it with the Cloud solution

Hello, Kindly read this documentation: https://confluence.atlassian.com/cloud/security-with-identity-manager-938859736.html

Hello, I think your JQL query would look like this: issuetype = <your subtask type>

Hello, You could use the Power Scripts add-on for it: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview Your JQL query would look like this: length < 101 key in silJQLExpression("length(description) < 101;", "") words < 101 key in…

Could you test it and say the errors you can see?

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 add a post function like this: #{STATE DATE} = currentDate(); You can find more info about post functions here:…

Hello, It is not possible anymore to switch to old UI on Cloud.

Hello, I attached a screenshot (icon in the red rectangle):

Hello, 1, If you want a user to enter a date, then you should create a screen with a date custom field. Then you get the value of this field in your script. 2, You already provided holidays in your script. Why is it not enough?

Hello, You should remove all permissions except Project admins and Project owners from the Transition Issues permission.

You are welcome!

Does your script compile? From what plugin is the Severity field?

Hello, You can not change the placement for the field.

Hello, It is on the Roadmap for next-gen projects. But not yet implemented: https://www.atlassian.com/roadmap/jira-software?_ga=2.22297852.675557620.1538152808-65270402.1526147845

Hello, Kindly read my article about integration tests in Jira https://community.atlassian.com/t5/Agile-articles/How-to-write-integration-tests-for-Atlassian-Jira-jira-func-test/ba-p/915593

Kindly make sure that you installed the correct version of Service Desk to your Jira. Here is the version matrix: https://confluence.atlassian.com/adminjira/jira-applications-compatibility-matrix-875304597.html

It was not obvious from your previous post that the Service Desk is installed. Have a look at this KB: https://confluence.atlassian.com/jirakb/service-desk-installed-but-not-enabled-found-dependent-enabled-plugins-for-plugin-800703376.html

Hello, You should add a post function with a code like this: #{custom field name} = #{custom field name};