How to add a task to the Current Sprint while in the Board View

[clarence]

Hi

Background 

Each morning our team reviews our sprint board in Jira (cloud / nextgen project). We organise the sprint board by user. Our sprint prioritises the work for the week. Each member gives an update on the issues/stories they are working on, we make sure it's in the right stage on the board and record any updates as comments. This works well.

Often there are adhoc (unplanned) stories that we have to include in the weeks sprint. Unfortunately this is really cumbersome and slow to do in Jira and requires leaving the board view, opening the  backlog view or in our case user story mapping view (easy agile plugin) adding a task there then navigating back to the board view. It seems like a oversight not to be able to add tasks to the live sprint from the board view. If each team member has updates to make it's really unproductive give the page loads and context switching and not a great user experience.

Ask

Is it possible to add stories to a live sprint in the board view are we are just missing a config? If it is not supported be great to know why this is? I am not sure conceptually why it wouldn't be available especially as you can add new tasks to a sprint via backlog view- just a very bad user experience. Implementation wise imagine very easy for a developer to include - simply  introducing the "Create Issue" button in the interface and setting the sprint to current sprint when a task is created. Similar to the  "Create Issue" button in the backlog view works.

Help and advice welcome.

[Atly Apps]

Hi @clarence, we've also wanted to be able to add issues to a board from within the board view, and we've just released an addon - Add to Board for Jira Cloud – which implements this functionality:

It's totally free for organisations with less than 10 users, and we've tried to price it very economically for organisations with more users. Please don't hesitate to contact us if you have any questions or suggestions.

[Derek Murray]

Seriously? This is a really basic feature and you are charging a fee for it? Surely I must have misunderstood.

[Jack Brickey]

@Derek Murray ,

keep in mind that @Atly Apps is an aftermarket app vendor selling addon apps to achieve things not offered or improved offerings beyond the Atlassian OOTB capabilities. They stay in business by selling their apps.

As I eluded to in my original post in 2020, adding issues in an active Sprint should be an exception condition. As such, encouraging this by making it easy to do within the active Sprint board is counter to best practices. Of course, creating an issue from any screen is simply a click away using the Create button on the top menu bar.

[Atly Apps]

Hey @Derek Murray, @Jack Brickey is correct that we're a third-party vendor creating apps to add additional functionality to Atlassian products.

Whilst we've tried to price it as economically as possible, running the app does require servers and other cloud infrastructure. Furthermore, a significant amount of engineering time has gone into making this app production-ready and usable in a variety of different different project/board configurations. We've also spent time working with Atlassian to identify and resolve several bugs that we encountered during development of the app.

We also hope to continue investing in the app with adding additional functionality and improvements over time. Please feel free to contact us if you have any further feedback or suggestions.

[Jack Brickey]

there is not a "create" or "add" to sprint capability OOTB. I think the reason is that you really shouldn't do that or at least make it a habit so don't make it easy. Just my interpretations of this. You can obviously add to a sprint from Backlog or directly from detailed issue view or the Create button.

[Jack Brickey]

?

[Derek Murray]

Agree with the OP and @Aleksander Altberg .  Everybody does it ... and has been asking for it for years.  That was one of the reasons we moved away from  Jira ... now that i've come back to it after a 4 year break I am surprised that it is still here as a "feature" ... a rather arrogant "father knows best" approach unfortunately.

Well articulated @clarence by the way.