Comments
-
Note too that the method has changed in the new issue view which we will all be relegated to this month. In the NIV you click on the type icon.
-
So filters have a number of purposes in Jira: * boards - all boards have an underlying filter that defines the issues that will be displayed * dashboards - use filters as part of what they display * saved filters - allow you to quickly access the issues you wish to see and how they are displayed So basically you will…
-
You can use Automation for this. trigger = issue created condition = if/else block and use JQL e.g. Summary ~ “flag-a” action = edit issue assignee
-
There is no means of determining this.
-
Hi Nate, welcome to the community. Jira doesn’t decide to make a user inactive. Admins are responsible for making this happen. There is no feature to automatically inactivate a user OOTB.
-
Hi Faith, so I’m not positive but I suspect that maybe you edited the filters associated with the boards causing the issues to no longer be visible on the board. First it is important to understand that boards are visual representations of queries and as such what is displayed on the boards is driven but the filters. with…
-
In Standard your best bet OOTB is to use Epic > Task > Sub-task
-
yep
-
I'm with Nic here... please explain "status ranking". you can certainly use the two-D gadget to show status on one axis and another field, e.g. Priority. It seems like Priority vs. Status is what you are looking for but unsure.
-
yep. i have one project where we use a Severity custom field.
-
please share a screenshot of this. if you truly own the dashboard you should be able to edit. if you cannot then I would refer you to Atlassian Support so they could log in and have a look. Does this happen on all boards? Can you try to copy the board and see if the issue continues? Do you have and addons that might be…
-
burndown - a graphical view of actual logged work vs. the plan. The chart illustrates a downward trend from "full" to "empty" where "full" equates to the total number of story points for a sprint and "empty" equates to completing all work. velocity - provides an average amount of work a team has demonstrated they can…
-
Hi Sophie, welcome to the Community! So you don't migrate "boards" but rather you migrate the issues from a Classic project to a Next-gen project. The process is a bit tedious and depends on the details of your starting point w/ the Classic project. This document should help you out…
-
i don't understand. If I create a JQL to illustrate sprint 179 it will present to me x-number of projects that are in that sprint. I can then go to each of these projects. How many projects are in fact in that specific sprint?
-
Any logged in user is just that - any user that is currently logged in. It is not associated w/ the default roles. So wherever this is used within a project permission scheme any user that is logged in will have those permissions. The default roles are defined here - admin > user management > site settings > product access
-
The report seems ok from what I can see.
-
You would need separate rules. There is not a multi-select feature in the transition trigger.
-
My first guess is that “Tested” status (SS1) is not mapped to “Testing” column (SS2). If the Tested status needs to go into that column go to board settings > columns and see if Tested status is hanging out in the unmapped section and drag it over.
-
there are a lot of posts similar to this in the Community that basically cover all typical causes. If you feel stuck at this point I would suggest contacting Atlassian Support. https://support.atlassian.com/contact/#/
-
“Status” rank? I am not familiar with that. You can use “issue” ranking but assume you are already aware of that and looking fo something else. But just in case - ranking-an-issue
-
That is not possible. Each project must have its own email. You could preprocess the emails outside of Jira and forward them to the appropriate project. Obviously accuracy will be completely dependent upon the accuracy/reliability of the content of the body.
-
That seems odd. It appears you are on a trial? Has that ended by chance? If not can you try to create a query that represent one of your sprints? Does it reveal data? Can you share a screenshot?
-
You can always contact support from a “billing” context. I believe but not 100% sure that you will have read access.
-
Yep customer profiles are not editable. Given the pages exist maybe they will be in the future.
-
I think you need to have the site admin dig into the logs.
-
Columns? Where are these columns? If you want to illustrate overdue issues on a board and this is a classic project then use card colors under board settings.
-
Things won’t disappear, at least for a few weeks though no real time commitment AFAIK on retention. Simply pay the bill or if that can’t be done for some reason open a support ticket with Billing and feel free to make it high priority.
-
I would think that the scrum board would be in one of the projects associated with the sprint. So if you use JQL to view each of the Sprint 179 issue you will know the project. Navigate there and see if it shows. If not the someone has created a private board under their profile possibly.
-
1) yes 2) yes
-
You should look to convert to cascading.