Alexey Matveev Expert

You do not set a field as required on a screen. You set it either in the validator for a transition or in the field configuration scheme. I guess, you set it in the field configuration scheme. And I guess the field configuration is used for all issue types in your project. You need to create two different field…

It is a custom field, which were created by a plugin. Plugins can lock fields, so that users could not change it.

You could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview Your JQL query would look like this: key in silJQLExpression('#{your custom field name} == <span>#{your custom field name}</span>',<span> </span>'project = TEST')

Hello, As far as I know, there are no plans to move next-gen projects to Jira on-prem.

Hello, You can not do it out of the box. You would need an add-on for it.

If my answer helped you, kindly mark my answer as accepted

You can find an answer here: https://community.atlassian.com/t5/Jira-questions/Give-a-JIRA-user-access-to-only-1-project/qaq-p/371132

Hello, I am not sure I understood your question. Do you mean that you made a field required in the field configuration scheme and now it became required for all issue types? If so then you need to create a different field scheme for the Problem issue type.

Hello, There is no way to recover a delete sprint. Only from a backup. You could also read this thread: https://community.atlassian.com/t5/Jira-Software-questions/Can-I-restore-a-Sprint-along-with-its-contents/qaq-p/599334/jump-to/first-unread-message

Hello, Kindly have a look at this KB: https://confluence.atlassian.com/jirakb/epic-tag-or-label-is-missing-on-sprint-board-779158640.html

It is not possible without an add-on.

Hello, Could you clarify your question?

Hello, You would need an add-on for it. For example, the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could write post functions for each transition leading from the To Do status to In Progress, In Progress to Done, Done to In…

Hello, Kindly have a look at this plugin: https://marketplace.atlassian.com/apps/20909/javamelody-monitoring-plugin?hosting=cloud&tab=overview You could also have a look at the Prometheus plugin: https://marketplace.atlassian.com/apps/1217960/prometheus-exporter-for-jira?hosting=server&tab=overview

Hello, You can use the Service Desk automation rule. You should create the Issue Created trigger, then add if issue match condition with a JQL like this: summary ~ "hostname down" and then add the Transition Issue action. You can find more info about Service Desk automation rules:…

Hello, Due Date is not a custom field, it is a Jira system field. You can not find it in the custom fields screen.

Hello, Timetracking is not available as of now. You can estimate tasks in Story Points.

Hello, You can not do it. The like operator is not defined for the status searcher.

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 write a script like this: string jql; jql = "project = TEST"; string[] keys = selectIssues(jql); for(string key…

There is not document like this. But here are some of the most important missing features: - no subtasks - no versions - no components - you can not change workflow - no select custom fields Of course, next-gen projects are under active development and maybe this features will be available later.

You can find ids of all transitions if you go to project settings -> workflows and open the required workflow:

Hello, That is the only way to migrate a classic project to a next-gen project. Just make sure that next-gen projects is a good match for you because next-gen projects lack lots of features of classic projects currently.

You can read more about this error here: https://confluence.atlassian.com/jirakb/resolving-permission-scheme-errors-838416389.html

Hello, It is just a warning. You can ignore it.

Например, JQL Search Extenstions: https://marketplace.atlassian.com/apps/1214791/jql-search-extensions-for-jira?hosting=cloud&tab=overview Там есть вот такая jql функция…

I see. Click on the issue in the backlog and move issue to the Closed/Done status in the issue preview, which is open in the right part of your screen.

You are welcome!

If my asnwer helped you, kindly accept my answer.

If you close this sprint, then these tickets will dissapear. Are you sure that you use sprints? Because if you do not use them then such tickets will dissapear after 14 days.

@Pavel Zrelov Тебя как раз могут редиректнуть сюда. Так что можешь продолжать задавать вопросы. Это нормально. Если вопрос по этой же теме, то задавай здесь. Если по другой, то отдельный вопрос нужно сделать.