Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
4,644,339
Community Members
 
Community Events
196
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
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 05, 2020

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
TAGS
AUG Leaders

Atlassian Community Events