Comments
-
Hello, It is not possible to have multiple board for a next-gen project.
-
You are most welcome!
-
Hello, Go to products -> application access. There will be questions about adding groups. You should accept the groups.
-
Hello, You need to copy this workflow, add the required transition and add the copied workflow to the project workflow scheme instead of the old one. There are limitation on editing draft workflows and you came across one of the limitations.
-
You can connect multiple statuses to the most right column. If my answer helped you, kindly accept my answer.
-
Hello, Only issues in the most right column of the board are considered completed.
-
Hello, You can not catch a email with Rest Api. 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 create a mail handler, parse your mail and create a user. You can read…
-
Hello, You will need to associate a new workflow to the project workflow scheme and on publishing this workflow Jira will ask you to associate all issues with absent statuses to a new one.
-
Hello, I am not sure what your requirements are. But basically you can not consolidate projects under one project. Have a look at the Structure plugin. Maybe, this plugin is what you are looking for. https://marketplace.atlassian.com/apps/34717/structure-for-jira-projects-at-scale?hosting=server&tab=overview
-
Hello, You would need to use organizations. You need to create two organizations: Country1 and Country2. Then you can include User1 and User 4 to Country 1 and User2, User3 and User4 into Country2. You can read more about organizations here:…
-
Open the Epic in the detailed issue view you will see a key there:
-
You are most welcome!
-
Hello, You would need a plugin for it. For example, you could use the Power Scripts plugin: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could create a post function with a code like this: summary = #{reviewer comments} + summary;
-
Hello, Go to board settings -> quick filters and add a quick filter something like component in ("name of your component") or key = EpicKey
-
Hello, Your licenses should work with your different server ID.
-
If you open an issue in the detail issue view, there must an option Convert to Issue
-
Hello, I am not sure what you exactly want. Do you want to log time automatically? If so, then you would need a plugin. You could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You can log time by a script like this: "2h",…
-
Hello, You should convert you sub-tasks to tasks first in the classic project and then move these tasks to the next-gen project. Here is more info on how to convert subtasks: https://community.atlassian.com/t5/Jira-questions/Converting-JIRA-sub-tasks-to-parent-issues/qaq-p/227858
-
Hello, It looks like you have a next-gen project. You can not change a lead for a next-gen project.
-
Hello, Try to import all projects and then remove the projects you do not want.
-
Hello, I would like to mention the Stucture for Jira plugin. This plugin represents issues as a hierarchy of issues. Many users of Jira ask about this functionality and Structure does it in a simple and yet flexible way. I began to use this plugin about 4 years ago and at that time I had problems with the plugin…
-
Push the edit button for the Browse Projects permission and choose the reporter and then the assignee
-
You could write a validator: string [] keys = selectIssues("customfield = yourvalue"); for (k in keys) { if (%k%.status == "Closed") { autotransition("Reopen", k); return false, "Issue " + k + " was reopened"; } }
-
Hello, You would need a plugin for it. For example, you could use the Power Scripts plugin: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could create a post function with a code like this: if (#{custom field name} == "required value") {…
-
Hello, Have a look at this KB: https://confluence.atlassian.com/jirakb/limit-restrict-user-s-project-access-280069544.html
-
Hello, Try to use this link: https://www.atlassian.com/ondemand/signup/form?product=confluence.ondemand,jira-software.ondemand,jira-servicedesk.ondemand,jira-core.ondemand,jira-incident-manager.ondemand&developer=true
-
Hello, You need to ask your current Jira administrator to include you to one of the groups, which has the admin permissions.
-
Hello, If you are an Administrator, it does not mean that you can see all tickets. You should make sure that you have the Browse Projects permission in all project.
-
You do not need to modify every issue. If you provide in the Browse Projects permission Reporter and Assignee then users will be able to see only issues to which they are assigned or they created. If there are other users, who must see all issues, then you also add the group of such users to the browse projects permission.
-
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 post function with a code like this: assignee = parent.reporter;