Comments
-
Hello, Only Jira administrators and system Jira Administrators can edit permission schemes.
-
Could you have a look at the Sprint value for an issue, which is absent? What it the sprint value there?
-
I am not sure, what you mean by missing issues. Here is how my Burndown chart looks like:
-
You are most welcome!
-
Hello, If you have a next-gen project, you can see it in the Burndown report. if you have a classic project, then you should see it in the Burndown chart. If an issue was added to a sprint, it will be written: issue added to sprint.
-
Hello, You could also do it with the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You can write a validator with a code like this: if (!(hasInput("worklog") and hasInput("originalEstimate"))) { return false, "<error message>"; } You can…
-
You can following this guide for migration: https://confluence.atlassian.com/jirasoftwarecloud/migrate-between-next-gen-and-classic-projects-957974933.html
-
Hello, You can take a backup for server in your Jira Cloud. Then you can install Jira Server, restore the backup from Jira Cloud and create a scrum project with sample data. After it you can create a backup of the Jira Server and restore it to your Cloud. Please, use a testing Cloud environment.
-
Hello, It means that you created a classic project. The Roadmap feature is only available for next-gen projects.
-
Hello, You can use Service Desk Automation feature. Create automation for Issue created trigger, then add the Issue matches condition with a condition like this: level = yourlevel Then add the Edit issue action and set the required value to the Manager field
-
Hello, You should use filter subscriptions. You can create a JQL filter to choose issues, which have been in a certain status for some period and then make a subscription for this filter. You can choose issue like this with a JQL query like this: not status changed from Open and status = Open You can read more about filter…
-
Hello, Could you make a screenshot where you can't see stories?
-
Hello, You can create a custom event, fire this event on the reopen transition and set the assignee as the event receiver in the project notification scheme. You can find more info here: https://confluence.atlassian.com/adminjiraserver/adding-a-custom-event-938847495.html
-
Hello, You can change the priority list. You can find how to do it here: https://confluence.atlassian.com/adminjiraserver/defining-priority-field-values-938847101.html
-
Hello, Kindly read this KB: https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html?_ga=2.222331986.856277697.1543736872-65270402.1526147845
-
Hello, The only way is to take a backup for Server, then install this backup on a temporary Jira Server, then import a project to this temporary Jira Server, then take the temporary server backup and import this backup back to Cloud. This procedure should be performed carefully, because there is a huge possibility of data…
-
Hello, You can add quick filters to filter issues in a Kanban board by labels. You could use JQL query like this for a quick filter: label in ("your label")
-
It is possible with ScriptRunner. You can hide the Move button and make your own button instead. Or you can see if an issue was moved, then clear the sprint field. But I do not have a ready made code for this requirement, unfortunately.
-
You are most welcome!
-
Hello, The behaviour is correct. Sprints do not belong to boards. If an issue is included in a sprint, then this sprint will be visible on all boards, which show the issue. You should edit the sprint field for your issue and remove the sprint from the XPTO sprint. In this case this sprint will not be visible in board A.…
-
Hello, Have a look at this KB: https://confluence.atlassian.com/jirakb/sidebar-menu-not-loading-in-new-jira-experience-943527764.html
-
Hello, If a user does not have a Jira Service Desk license, then the user has access to Service Desk feature only via the Portal
-
Hello, That is right. You should use webhooks for it.
-
Try a query like this: project = test and ((issuetype != Epic) or (issuetype = Epic and "Epic Status" is not EMPTY ) )
-
You are most welcome!
-
The screenshot you provided is the new Issue View and you should use the Issue Layout settings to handle it. The issue detail view only influences the screen, which was on my screenshot. You can get it, it you go to backlog and choose one of the issues there.
-
@Mandia the DueDate field is not updated automatically. It means you have a script somewhere , which updates the Due Date field. You should find it.
-
Do you meant that you have Jira Cloud? I gave you links for Jira Server. On Jira Cloud your instance will be updated automatically. You do not need to buy anything or ask for update. Another thing that you can not ask Atlassian not to update your Jira Cloud instance, your Jira Cloud instance will be updated anyway. For…
-
You can add a JQL like this to the filter of the required board: and "Epic Status" is not empty
-
You should ask the project administrator of the required project to grant you permissions.