How do I distinguish/identify different jobs between occupations in Jira



  • Suppose my team is going to develop a system, which includes sign up, login, password recovery and lots of other modules.

    There are an UI designer, a PO, a front-end engineer and a back-end engineer in my team. To track their work, I could create some stories, e.g. sign up jira story, login jira story, password recovery jira story

    enter image description here

    and then create 3 groups of sub-tasks under corresponding jira story respectively. For example, under jira story sign up, I create sub-task sign up - product definition for PO, sign up - Front-End for front-end engineer, and so on ...

    under jira story login, I create sub-task login - UI for my UI designer, login - Back-End for my back-end engineer, and so on ...

    Each Jira sub-task is also tagged a "Component/s" field correspondingly, for example, sub-task login - UI is tagged UI.

    Is the process above a common way to track the development of a project?



  • Is the process above a common way to track the development of a project?

    No. In Jira, you have a status field. This field is configurable in a workflow. The administrator can define what options exist and how you can change from one option to another.

    For example, your Aministrator could have used the options "Requirements Gathering", "UI/UX Design", "Coding", "QA", "Complete" and they could have made it so that you can skip "UI/UX Design" and go straight to "Coding", but you cannot skip "QA". Or they could use any other workflow you can come up with. I think I said it in another question, Jira is the tool that you need to configure to fit your companies workflow.

    I have seen two practical reasons for subtasks: technical reasons where you need to reference two distinct numbers even though it's the same story (for example frontend dev and backend dev both need an id for their commits, but don't want to use the same to not mix things up) or actually independent tasks that can be carried out asynchronously.


Log in to reply
 

Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2