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

[Sanara Premaratne]

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.

[Nic Brough -Adaptavist-]

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.