Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Jimi Wikman
    Jimi Wikman

    When to use Task in Jira - a practical approach for development teams

    • Interresting 1

    One of the most common questions I get is when to use the issue type Task in Jira. This is not surprising since Jira is intentionally not defining how to use the issue types and their hierarchy. This is to avoid restricting the users from building a way of working that is best suited for them. In this article I will explain my thoughts from a development perspective.

    As I have described before in the article "Setup Jira and Confluence for success - Part 2: Defining Jira Issue Types" there are three levels in the standard Jira hierarchy. Task would fall into the middle level and the sub-tasks would be the last level. This means that Task would be on the same level as a Story and that is what we can start from when defining what should a Task be for in a development perspective.

    In a normal workflow for development we would have a Story issue created as a result from the requirement, or need if working Agile, process. So the Story would map towards a need or requirement and as such we would have a workflow where we can trace actions from idea all the way to production.

    jira workflow.jpg

     

    Then where do Task fit into that workflow?

    In most cases it will not as a task would not be a part of a requirement or a need. That is what a Story is for. A Task is most likely only going to be used for Task management rather than as a workflow. This means that a Task would most likely be something that have limited states such as New, In Progress and Closed. It might even just have New and Closed to be even closer to the way task management is defined.

    In a development situation where you need to have a workflow a Task is best suited for activities that are not directly related to the workflow. Things like setting up environments, prepare presentations or Demos and even things like buying cake for the next retrospective (which of course always is mandatory!).

    If you use Tasks in this way, then sub-tasks would follow the same pattern. For a development task for example you might need to schedule a meeting with an external vendor to go over the API details for an integration. For a test task you might need to organize a workshop for end to end testing across multiple teams and systems and so on.

    In short, my definition is that Tasks are used for internal task management that is not directly related to the workflow.

    Do you agree or disagree?

    Edited by Jimi Wikman


    • Interresting 1


    User Feedback

    Recommended Comments

    There are no comments to display.



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By ©Jimi Wikman
      The requests to get Portfolio for Jira for Cloud users have been loud and finally Atlassian released a Cloud version. They also made a very odd choice to rename Portfolio for Jira to Advanced Roadmaps and place it behind the Cloud Premium barrier.
      Portfolio for Jira has long been the better choice for Jira Server and Jira DC users. The features have been perfectly suited for managers to keep an overview over large programs and initiatives with relative ease. As such it has been the envy of Cloud users for years and it comes as no surprise that Atlassian would port this to Cloud given their focus on the cloud platform lately.
      Renaming Portfolio for Jira is also no surprise as it confuse managers with two portfolio products where the high level Portfolio tool Jira Align is the product Atlassian seem to want to focus on. Renaming it to Advanced Roadmaps is however a very strange choice as it is not a simple roadmap tool. It also make the naming confusion shift from Portfolio to Roadmaps as Cloud users have been using the limited Roadmaps feature for quite some time.
      The new Advanced Roadmaps is only available for Cloud Premium users. This makes sense as Atlassian want to push users into their new price model. Currently there is not much that would warrant double the price for Cloud Premium so Atlassian need something that is enticing enough for users to make the shift. Advanced Roadmaps could be one of those features, but they need more as Advanced Roadmaps cost $2.3/user and month at it's lowest level and Cloud Premium cost an additional $7/user and month.
      Feature wise Advanced Roadmaps is still great with the two main selling points of great overview and the ability to scale the issues with more levels. Here are some of the selling points from Atlassian:
      With the changes coming to Roadmaps where all projects will get them, and not just Next-Gen projects, combined with the promise that Advanced Roadmaps will somehow be connected to a more comprehensive whole this could be a pretty good thing for Cloud Premium users. Adding Advanced Roadmaps to Cloud Premium will now add the ability to scale issue types beyond the standard 3 levels, which is something people have asked for for a very long time.

      Will it be enough to warrant the high price tag for Cloud Premium? I doubt that as Advanced Roadmaps is only really useful when you pass a certain number of teams. Doubling the price tag will probably discourage most low to mid-range clients. The fact that you can only have a 7 day test version and that you need to setup a new cloud instance to even test this if you are on a regular cloud plan is also a problem. With more features added into Cloud Premium however I think more and more will make the shift over to that.
      Overall this is a good new addition and package it with the Cloud Premium offer will make it more accessible and therefore used, which is a good thing. It's a bit sad to see Atlassian being so aggressive in their way of forcing cloud users into their Premium tier that is making some old customers a bit annoyed, but I think it will be good in the long run.
    • By ©Jimi Wikman
      This video is about Halp's integration with Microsoft Teams. If you'd like more information or to try Halp in Microsoft Teams visit https://halp.com/microsoft-teams
    • By ©Jimi Wikman
      Atlassian has announced that they have acquired Halp. Halp is an interesting take on support for Slack that allow you to create support tickets directly from conversations in Slack. As Halp can also be integrated with Jira Service Desk it makes sense for Atlassian to make the investment to purchase Halp to further strengthen their service portfolio on the support side.
      Halp have made a bit of an impact in its only 12 months life span and with the simplicity of just posting an emote in Slack to create separate support tickets it has been a hit. Good integrations with Jira Service Desk and Zendesk has of course been a big part and now with integrations to Microsoft Teams it is even better.
      Not only will Halp make it so much easier to keep track of support questions in Slack, but by integrating with other tools such as Jira Service Desk, then you have a powerhouse. It will update on both sides of the integration allowing you to meet your clients where they feel most comfortable and still maintain proper workflows. You can even connect it to Confluence or Slack messages to create knowledge bases.
      This is of course another step to connect closer to Slack that purchased the rights to Atlassians previous chat products. Naturally Slack is very happy about this acquisition:
      In the future we will see deeper integrations with Jira Service Desk and Confluence for sure, but there are hints forr new integrations with OpsGenie and Trello for example. It will undoubtedly be an interesting journey to follow in the future.
       
       
    • By ©Jimi Wikman
      Dedicated to developers, business analysts, testers, and test managers, Requirements and Test Management for Jira combines all aspects of software development, including requirements, tests, and bug reporting, into one intuitive tool.
    • By ©Jimi Wikman
      As an Atlassian Platinum Solution Partner Enterprise and a Platinum Top Vendor in the Ecosystem, we’ve been working hard on enhancing the use of Jira Software for over 2500 business teams around the globe. This app adds Requirements, Test Plans, Test Cases and Test Executions panels to your software project in Jira and thus allows you to track the whole development process from collecting requirements to going to production in a single place.   Try the app out for free on the Atlassian Marketplace:    Follow us on other channels:
      https://www.linkedin.com/company/devi... http://twitter.com/deviniti_voice http://facebook.com/DevinitiPL
×
×
  • Create New...