We use Jira Next-Gen with Atlassians cloud-hosting.
I moved Issues from "in progress" into "Done" state. However, when I want to close the current Sprint, Jira still reports all Issues as "open" and asks me to transfer them over into the next sprint.
Within the Jira Next-gen project there is no option to "close" an issue.
If "done" is not the right state to complete an issue, how can I achieve that?
Try checking your Board for the active sprint. The columns in the board represent the available statuses and only the last column (rightmost) is the 'complete' state.
Do you have a status to the right of 'Done' on the board? If so you can try dragging 'Done' to the far right which should fix your issue.
Related
I have an advanced capacity planning extension that replace the work details panel in the current iteration back log panel.
is there a way to register to workitem change event? currently thr only event work is the work item selection change event which is not relevant.
thanks
dror
According to your title, you want to enable live updates to automatically refresh your backlogs when work item changes occur.
This is not available at present. You still have to press F5 to see the latest changes.
There is already a related user voice, kindly upvote it and our PM will review any feature request:
Button to refresh the backlog, or ability to auto-refresh backlog
https://developercommunity.visualstudio.com/idea/501639/button-to-refresh-the-backlog-or-ability-to-auto-r.html
I use a Kanban board with a Scrum development project. I've seen that Jira can automatically ask the user whether or not to close the primary item; when the last of its sub-tasks are closed. But this isn't happening with my Kanban board.
What triggers Jira explicitly to ask the user whether to close the main item? Does this need to be configured?
In the end, I fixed this by installing an add-on, Adaptavist ScriptRunner for JIRA.
This allows you to create a post function that updates the main item when the status of a sub-task changes.
I wanted to only close the main item when all sub-tasks were closed, not whenever one sub-task is closed. To make that work, I added a condition so the main item can only be closed when all sub-tasks are closed. I could create this condition even without ScriptRunner.
I didn't have to write a script or do any other programming. It was pretty issue once I installed ScriptRunner.
This can be done in the post function. Just create a small script that checks if all of the subtasks are closed, which can then push the parent task in the necessary transition or else you can throw an event when the sub tasks are closed and use the Auto Tranisiotn Listener in JIRA Toolkit to do the transition.
I'm trying to have my company transition to JIRA from email for bug tracking purposes, and I can't figure out one thing: why JIRA (and BitBucket's Issues, which is sort of a limited version of JIRA) don't have a "Ready for retest" status.
I imagine the flow works like this:
Bug is reported
Bug is handled by developer
Developer marks bug as ready for retest
Tester tests, marks "Resolved" or "Closed" if all is OK, otherwise back to "Open".
Apparently I misunderstand something or other people don't work in the same way. What's the correct workflow status for the testers to retest the bug?
You, or your jira administrator, can create your own status in Jira. Look in Jira adminstration/ issues/ issue attributes and there you can add a status.
Then you still need to add that status to your project workflow, but that is another story.
Here is a link to help with all of it: https://confluence.atlassian.com/jirakb/define-new-status-or-steps-in-jira-workflow-718835875.html
Some organizations use the "Resolved" state to mean what you do by "ready for retest", then move the bug to "Closed" when the retest is successful. This would let you use the default workflow without adding states.
I looked through the hotkeys, and can not find a way of changing the status. This would help me out seeing my timeclock system is integrated in with the "In Progress" status ( I have it set up where if a ticket's status get's put into "In Progress" it clocks that user into that job, And when one moves from "In Progress" to something else, it clocks me out of it )
To change a tickets status without your hands leaving the keyboard, hit the period (.) key and then type the name of the status you want to transition to. Some JIRA installations or situations may require you to use (gg) instead of (.) so try that too. This will work from the search results screen, agile boards, or just about anywhere where you can select a particular issue.
Be careful to make sure the result that you select shows up under the Workflow heading just in case there are other related actions that are worded in a similar fashion to your status.
There is a status in my JIRA instance called "Ready For Test" at which the tester would validate and close the jira. I need to know the amount of time the JIRA is in that particular status since it was moved from "In Progress" to "Ready to Test".
Is there a JQL query that can do it? I need this time field to be exported to Excel as well so that I can name and shame people and ask them to close the JIRAs as soon as they can.
I don't think it is possible on clean Jira installation. There are two plugins I know providing this kind of functionality:
Time in Status - self-explanatory
Enhancer Plugin (sorry, can't post more than two links) - adds a configurable time in status custom field, bt if I remember it correctly, it can display value only after you leave the status.
These are both paid, so that can be an issue.
Another option (if you're not using OnDemand) is the Script Runner Plugin. This plugin will allow you to create your own workflow postfunctions so you can store the "Ready to Test" transition date to one custom field and either calculate time and write it to another custom field when leaving that status or write a scripted field that will calculate and display current time since entering status. This solution is free (not counting your time to implement the functions).
Thanks #SilenyHobit for the idea. Here is what I've done:
First installed JIRA Suite Utilities plugin (its FREE)
Added a custom field called RFTDate (date type control)
Added a post function in RFT transition to update RFTDate with current datetime
Voila!!!
As an alternative, you can use Status Time Jira app. It provides reports on how much time passed in each status.
Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports by any field(eg. average in progress time by project, average cycle time by issue creation month). And all these are available as gadgets on the dashboard too.
Here is the online demo link, you can see it in action and try.
As a free solution, you can try the limited version Status Time Free.