XMLWordPrintable

Details

    • Suggestion
    • Resolution: Done
    • Not Evaluated
    • 3.13.4
    • None
    • None
    • None

    Description

      We're using JIRA tasks heavily for (internal) project management. From daily work I'm struggling with three issues:

      • A lot of bugs/tasks are effectively blocked by open issues e.g. in Qt. We're not really sure how to best handle this on the personal level: We want to keep the tasks around, because they are something we have to ensure that is fixed e.g. for a release. On the other side keeping them in the 'open' state pollutes your task list. For some of use tasks like these make up >50% of the open tasks.
      • It's hard to keep a list of tasks around that you e.g. want to talk about in the next project meeting. You can of course link to them e.g. from an artifical "To discuss" task, but adding relationships is actually somewhat time consuming.
      • The Project/Component levels structures are too coarse. E.g. all the Qml (Text Editor, QmlDesigner) support in QtCreator is right now one big component. It would fit us much better if e.g. the PropertyEditor in QmlDesigner in QtCreator would be one 'component'.

      A solution that might help mitigate all three problems would be support for tags. This would allow individual projects to invent e.g. their own 'task states' without necessarily changing the fundamental work flow underneath. E.g. I'd add 'blocked' and/or 'todiscuss' tags by just adding them to a text input field, and then could easily filter for these specific tags. The same for 'sub-components': propertyeditor would be one tag which we could easily filter for.

      Btw, is this something I should rather bring up for the JIRA product itself?

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            mkeir Mark Keir
            kkohne Kai Köhne
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes