Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What are the attributes that needs to be included for Tasks and user stories in the Kanban Process?

The JIRA Backlog has different kinds of issues. They are Epic, Stories, Tasks and Bugs. 

Each of this issues have their unique features. 

The Kanban Process consists of several steps such :To Do, Documentation, Development , Review , Review Failed, Test, Reopened after Test, Ready for Staging, Released to Staging, Released to Production 

When the issues are brought to the Kanban Board, they are required to fill certain attributes to go to the next level.

1 answer

0 votes

For a Kanban story, the required "attributes" are

  • a description of what needs doing, so someone can do it (this can be as simple as the summary field),
  • a status, so that everyone knows where it is in the process
  • a single assignee, so that everyone knows who is responsible for getting it done (should be entered at "we started working on it" at the latest)

And that's pretty much it.  Your process might require more data, but that's up to you to define.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

184 views 1 6
Read article

Atlassian Community Events