Issue Complexity vs Severity

[JScott]

Hey Team Taiga,

As soon as I heard about Taiga I hosted it for our company and started using it on my Scrum team. I love the customization and so far it's well worth the investment of getting an ansible playbook running for an alpha product :P

However, there's one thing that irks me every time we use issues. With Priority being an attribute, Severity seems redundant. We've re-purposed it to mean Complexity which is a lot more useful in tandem with Priority. Given Taiga's amazing customization options I was wondering if it'd be possible to rename the column. If not, is this perhaps a change worth making across the board? It seems more in line with what we'd care about as an Agile team.

[Jesús Espino]

Hi JScott,

First, thanks for using Taiga and send us feedback :)

I explain a lot of times the difference of priority and severity, are
really different, urgent and important aren't the same. But I like
your idea of allow to change the "label", and then the meaning, of the
columns. Priority, severity or type are util for some people, but as
you say, you may prefer complexity or other thing.

We will add this to our backlog (there are a lot of user stories with
more priority than this, but in any time will be implemented). The
final solution will be editable and hiddeable type, severity and
priority.

Greetings and thanks for your feedback.

> --
> You received this message because you are subscribed to the Google Groups
> "taigaio" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to taigaio+u...@googlegroups.com.
> To post to this group, send email to tai...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/taigaio/49293827-38e6-45e4-8901-3db062cbf092%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.