I more often want to work on new tickets straight away than having them for later and rather decide which ones can go on the Backlog pile than the other way around.
Currently when creating a new ticket in a next-gen project I ...
Is there a setting to have tickets created saved to the Board instead of the Backlog so I can skip steps 2 & 3?
When you create a ticket, there should be a field called "Sprint".
If this isn't in the list, go to Project Settings --> Issue Types --> whichever Issue Type you want to edit --> and add the Sprint Field in the list.
Save changes and you're done.
Now, when you create a ticket, whenever you are on the Board or the Product Backlog, you can select the Sprint (including the current Sprint).
I just disabled the Sprint Feature and then I am unable to add them to a Sprint immediately, so yes, you would need to have the Sprints enabled to use this.
However, if you check your Board again, you can also create a ticket there in your current iteration if you have no Sprints enabled.
You can see the list with the issues that are on your Board, when you are looking at your Backlog. Under this Board, you can see the + Create issue button.
This would only provide the summary, though, but it's visible on your Board immediately as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks again for taking the time.
My idea is more towards
-> I am in Project A (or in a subtask, etc. in Project B; just not on the Board) and want to create a new task in Project B without navigating away from the current screen
-> I hit the "c" key and create a new task in Project B
-> the new task should be on the Board of Project B, not (hidden) in the Backlog
Hope that makes sense.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It does make sense :-)
So, while anywhere in Project A, you want to create a ticket in the Board of project B.
If you have Sprints enabled in Project B, this is possible.
If you don't have it enabled, I'm afraid it's not possible like that. You would expect to have it possible to add a ticket to the current iteration. I assume that the reason is that if this is developed as you describe, a Kanban Board will never be empty, undermining the value of iterations.
But maybe you can add a ticket on https://jira.atlassian.com/ and request this feature for the Next-Gen Board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can create a ticket directly in the board column by hitting the plus sign in each column. At first, you are limited to just selected issue type and writing a summary. Just open the ticket to fill in all other information and custom fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure, thanks Jason.
But I am creating tickets against that project from wherever I am in my Jira instance by hitting "c" and would like to have these tickets not "hidden" in the backlog.
Your method would means:
What I want is
;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here, would love to know if anyone has discovered a workaround that doesn't involve Sprints.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.