Taiga-front: Kanban view for the issues

Created on 20 Jun 2015 · 17Comments · Source: taigaio/taiga-front

Would it be possible to enable the Kanban view for issues (the way it currently looks for user stories)? I find the current Excel-like list very difficult to manage around.

enhancement taiga-6-clean-up

Source

metakermit

👍5

Most helpful comment

@knocte An issue can already be promoted to User Story in the issue detail.

True! I was a newbie when I wrote that. Thanks.

But after some weeks of using Taiga, I find a bit annoying that the user-stories spawned from issues are not in sync automatically, i.e. if the user story is marked as deployed/archived, the issue should be automatically closed. Has somebody reported this suggestion/improvement?

knocte on 6 Oct 2016

👍8

All 17 comments

Hello @kermit666 ,

Actually there is now way for doing it, a possible workaround could be using the "promote to user story". I'm tagging your idea as enhancement and the development team will review it to see if it can be included in Taiga core.

Regards!,

superalex on 22 Jun 2015

👍1

I think there might be a misunderstanding about what constitutes an issue in your mind.

To me, an issue is a bug or problem that needs to be fixed. A user story is something else. Turning an issue into a user story is probably useful, but should not be the only way to get an issue into your kanban.

mkaito on 24 Nov 2015

Just a small remark, issues in Taiga can have different types (customizable via the admin interface), by default they can be bugs, questions or enhancements so depending on your workflow it could make sense to transform them to user stories or not.

superalex on 25 Nov 2015

Then it makes sense to use issues as more generic entities. All the more reason to use issues directly on the kanban board (and probably on the taskboard as well).

The issue we've been running into is dealing with bigger stories (aka epics). I know you guys have it in the backlog. How do you deal with that internally? I know you use Taiga to run Taiga development. Do you use an external tool to outline stories and only feed properly sized stories into Taiga?

mkaito on 25 Nov 2015

Actually we are just using a mix of tags and customized status to organize all our our user stories. We are using no external tool.

Regards!,

superalex on 26 Nov 2015

Just decided to try out Taiga.io today. I was quite disappointed when I discovered issues are not supported in the Kanban. After some Googling which lead me here, it seems I'm not the only one.

markslwong on 18 Feb 2016

Same comment for me, we should be able to put issues into the Kanban without promoting them as user-stories.

xens on 16 Mar 2016

The current kanban is for user stories, it has one column per user story status, so you have a kanban view for issues list.

bameda on 17 Mar 2016

bameda: I can't find a kanban view for issues into Taiga, am I missing something ? The only view that I have for issues is a list.

This issue looks more like a feature request to me

xens on 17 Mar 2016

Sorry, what I mean is that in the current kanban can not mix stories and issues because states are different between them. So you need a different kanban for issues that currently doesn't exist.

bameda on 17 Mar 2016

Any updates on this?

+1 to the idea of "promote to user story"

knocte on 13 Sep 2016

@knocte An issue can already be promoted to User Story in the issue detail.

Xaviju on 13 Sep 2016

@knocte An issue can already be promoted to User Story in the issue detail.

True! I was a newbie when I wrote that. Thanks.

knocte on 6 Oct 2016

👍8

Wouldn't it be possible to create a kanban view mode for the Issues module so people can switch between list and kanban view based on their needs? And I don't mean using the existing kanban module to show issues, but a new feature in the Issue module itself.

Because I see problems with using "promote to US" since the US is not connected to the issue in a way that closes the issue when the US closes. Many maual tasks are needed to handle both the issue item and the US item. Also, the project might not want to mix "proper" US and issue US in the same kanban view. Sure, you can tag and filter, but that is one more manual step that I don't want.

Since the code for a kanban view exist, implementing a new view mode for issues would hopefully not be that hard.

gangefors on 23 Mar 2017

👍5

No news on the subject? To me it seems stil actual... :(
Both the kanban view for the issues and the synching between an issue and a related US. What about, when you close an US, to display a popup asking the final state of the related issue?.

vratojr on 15 Oct 2018

👍1

We have been doing some housecleaning work prior to Taiga6 upcoming release and we are rejecting old issues that we didn't correctly attend back then. Since Taiga6 brings a significant UX/UI rework, we encourage you to wait and see if Taiga6 satisfies this need and open a new issue if that's not the case. This time we will make sure to review it when it comes through. Thank you very much on behalf of the Taiga Team!