Recent changes to wiki

Search modified by Rebecca Shalfield

2019-10-28T21:44:21.759000Z

--- v1
+++ v2
@@ -1,5 +1,4 @@
-
-Search
+**Search**

 Kanbanara features an extensive search facility allowing you to search for a phrase in all or a named card attribute.

Workflow modified by Rebecca Shalfield

2019-10-28T21:42:16.584000Z

--- v1
+++ v2
@@ -1,13 +1,14 @@
-
-Workflow
+**Workflow**

 Within Kanbanara, a project?s workflow is completely dynamic. It can range from something as simple as “To Do”, “Doing” and “Done” upto a workflow consisting of 12 steps, each step consisting of a main column, a counterpart column and a buffer column.

 A step can be thought of as a combination of upto three state columns, Main and Counterpart holding cards waiting to be processed and the Buffer, holding processed cards waiting to be moved onto the next step. A step can be given a name such as “Backlog”, “Specify”, “Implement” or “Validate”. Each state column within the step can be given a name as well as whether it is owner-, reviewer- or quality assurance-centric. A state column?s centric setting will dictate how cards are handled when they reach the review/QA stage(s).
-Metastates
+
+**Metastates**

 Kanbanara posseses 23 built-in metastates - untriaged, triaged, backlog, defined, analysis, analysispeerreview, analysed, design, designpeerreview, designed, development, developmentpeerreview, developed, unittesting, unittestingaccepted, integrationtesting, integrationtestingaccepted, systemtesting, systemtestingaccepted, acceptancetesting, acceptancetestingaccepted, completed and closed. Any custom state you define and use in your workflow must be mapped onto the most appropriate metastate.
-States
+
+**States**

 At Kanbanara?s heart is its kanban board. The states in your workflow can be altered at any time to suit your particular needs, even after your kanban board is fully populated with cards.

@@ -22,51 +23,63 @@
 User can set a time period for the number of cards in closed state they want displayed.

 If a card has both an owner and a co-owner, both a reviewer and a co-reviewer or both a quality analyst and a co-quality analyst, then setting the state must be done by both team members before the card can be automatically moved to the next state. Should a card have been moved to the next state by one team member only, the card may then appear in the column?s waiting section depending on whose kanban board you are currently viewing.
-Default Steps and Columns
+
+**Default Steps and Columns**

 By Default, the workflow in Kanbanara consists of eleven steps - Planning, Backlog, Specify, Design, Implement, Validatation - Unit, Validatation - Integration, Validatation - System, Validatation - Acceptance, Completed and Closed.
-Planning Step
+
+**Planning Step**

 The Planning step consists of a main column, Untriaged, and a counterpart column, Triaged.
-Backlog Step
+
+**Backlog Step**

 The Backlog step consists of a main column, Backlog, and a buffer column, Defined.

 In the Backlog column are displayed those cards in your backlog. Normally, such cards have yet to be assigned a release or iteration. On the kanban board, such cards in the backlog state may appear in one of two locations - Either in the Pyramid section (if already put in order via the Backlog Pyramid) or in one of the Priority section as per cards in other states.

 In the Defined column are displayed any cards duly defined to be worked on next, normally for a particular release (and iteration) and are awaiting their move into the Analysis state when Work-In-Progress limits allow. In Scrum terms, you can think of this column as the Sprint Backlog. Defined is a buffer state.
-Specify Step
+
+**Specify Step**

 The Specify step consists of a main column, Analysis, a counterpart column, Analysis Peer Review, and a buffer column, Analysed.

 In the Analysis column are displayed any cards currently being analysed.

 In the Analysed column are displayed any cards that have been analysed and are awaiting their move into the Development state when Work-In-Progress limits allow. This state is the second half of the specify step. Analysed is a buffer state.
-Design Step
+
+**Design Step**

 The Design step consists of a main column, Design, a counterpart column, Design Peer Review, and a buffer column, Designed.
-Implement Step
+
+**Implement Step**

 The Implement step consists of a main column, Development, a counterpart column, Development Peer Review, and a buffer column, Developed.
-Validate - Unit Step
+
+**Validate - Unit Step**

 The Validate - Unit step consists of a main column, Unit Testing, and a buffer column, Unit Testing Accepted.

 When assigning a reviewer to a card, the reviewer?s names are placed in order of least busy to most busy, with a card count after their name, thereby allowing the least busy team member to be more likely chosen. When a card reaches the Testing state, the owner and reviewer effectively switch roles, with the reviewer requested to work on the card and the owner a passive observer. As a reviewer, you can see what work is heading your way as such cards appear greyed out in the states preceding Testing. This state is the first half of the validate step.
-Validate - Integration Step
+
+**Validate - Integration Step**

 The Validate - Integration step consists of a main column, Integration Testing, and a buffer column, Integration Testing Accepted.
-Validate - System Step
+
+**Validate - System Step**

 The Validate - System step consists of a main column, System Testing, and a buffer column, System Testing Accepted.
-Validate - Acceptance Step
+
+**Validate - Acceptance Step**

 The Validate - Acceptance step consists of a main column, Acceptance Testing, and a buffer column, Acceptance Testing Accepted.
-Completion Step
+
+**Completion Step**

 The Completion step consists of a main column, Completed and a counterpart column, Closed.

 As all cards will eventually end up in the closed state one way or another, unless of course deleted, the number of cards displayed can be restricted to those cards closed in the last five years right down to those closed within the last hour.
-Why No ‘Blocked’ State?
+
+**Why No ‘Blocked’ State?**

 Kanbanara has no need for a ‘Blocked’ state as a card can be blocked either by its children or via the setting of a blocked attribute on a card itself. Any cards thus blocked automatically appear in a special blocked section in the appropriate column on the kanban board, thereby allowing you, for example, to have a card in both ‘Development’ and ‘Blocked’ at the same time.

API modified by Rebecca Shalfield

2019-10-28T21:38:48.771000Z

--- v1
+++ v2
@@ -1,16 +1,18 @@
-
-API
+**API**

 Kanbanara possesses an API to allow client software to interact with the product:

-    rest_api_get_token
+** rest_api_get_token**

-Inputs: username, password Output: token
+Inputs: username, password
+Output: token

-    rest_api_get_projects
+**rest_api_get_projects**

-Inputs: token Output: projects
+Inputs: token
+Output: projects

-    rest_api_get_project_members
+**rest_api_get_project_members**

-Inputs: token, project Output: usernames
+Inputs: token, project
+Output: usernames

Quality Assurance modified by Rebecca Shalfield

2019-10-28T21:35:28.094000Z

--- v1
+++ v2
@@ -1,10 +1,10 @@

-Quality Assurance
-Quality Analysts
+**Quality Assurance**

-    Up to two quality analysts can be assigned to a card.
+**Quality Analysts**

-    Warning given if in a Quality Assurance (QA) column but no quality analyst assigned.
+*     Up to two quality analysts can be assigned to a card.
+*     Warning given if in a Quality Assurance (QA) column but no quality analyst assigned.

 Each card can be assigned up to two owners, up to two reviewers and up to two quality analysts, thereby assisting with either pair programming or pseudo team members such as the current incumbent of the service support liason role.

Themes modified by Rebecca Shalfield

2019-10-28T21:34:26.939000Z

--- v1
+++ v2
@@ -1,4 +1,3 @@
-
-Themes
+**Themes**

 Kanbanara features a theme creator that allows you to change the colours of the states and cards on the kanban board.

Reports modified by Rebecca Shalfield

2019-10-28T21:33:15.522000Z

--- v1
+++ v2
@@ -1,4 +1,3 @@
-
 Reports
 Built-In Reports
 Costs Report
@@ -9,7 +8,8 @@
 Escalation Report
 Root-Cause Analysis Report
 Backlog Trend
-Custom Reports
+
+**Custom Reports**

 In addition to a number of built-in reports, Kanbanara allows custom reports to be defined using a language similar to that used for rules:

Team Members modified by Rebecca Shalfield

2019-10-28T21:30:46.455000Z

--- v1
+++ v2
@@ -1,40 +1,43 @@

-Team Members
+**Team Members**

-    New team members must be invited to join team by existing team members.
+*     New team members must be invited to join team by existing team members.
+*     Ability to see the corresponding kanban board for anyone else on your team.
+*     With the ability to add a pseudo user as a Team Member and as an owner of a card, the handover from one real Service Support person to the next will be greatly simplified.
+*     Your own avatar can be uploaded.

-    Ability to see the corresponding kanban board for anyone else on your team.
-
-    With the ability to add a pseudo user as a Team Member and as an owner of a card, the handover from one real Service Support person to the next will be greatly simplified.
-
-    Your own avatar can be uploaded.
-
-Roles
+**Roles**

 The settings for a given project can be restricted by allocating one of four roles - project manager, deputy project manager, team member or guest - to a given team member.
-Owners, Reviewers and Quality Analysts
+
+**Owners, Reviewers and Quality Analysts**

 Each card can be assigned up to two owners, up to two reviewers and up to two quality analysts, thereby assisting with either pair programming or pseudo team members such as the current incumbent of the service support liason role.

     Supports Owner and Co-Owner, thereby allowing a card to be owned by the current Service Support person and co-owned by one of your fellow team members. When a card is in a Review/QA state, its owner will only get a placeholder card to indicate another is reviewing it. Reviewer/QA role comes to the fore only in a Review/QA column.

-Owners
+**Owners**

 Each card can be assigned up to two owners, thereby assisting with either pair programming or pseudo team members such as the current incumbent of the service support liason role.

 With the ability to add an ‘Support Person? as a Team Member and as an owner of a card, the handover from one real Support person to the next will be greatly simplified.
-Avatars

-A team member?s avatar may be uploaded and utilised, for example, on the avatar kanban board.
-Personal Work In Progress
+**Avatars**
+
+A team member's avatar may be uploaded and utilised, for example, on the avatar kanban board.
+
+**Personal Work In Progress**

 Personal Work In Progress (WIP) limits override the global ones on a team member by team member and project by project basis should the project manager allow it.
-Subteams
+
+**Subteams**

 One or more subteams can be added to a project. Any of a project?s subteams can then be applied to a card in that same project, allowing you to display only those cards for a particular subteam on the kanban board via the subteam filter setting.
-Absence and Absenteeism
+
+**Absence and Absenteeism**

 The Absence page allows you to enter the start and end date of your next absence from work, so as to alert others to your absenteeism, especially if you are a reviewer or quality analyst for one of their cards. Each team member has the ability to enter the next date range that they will be on holiday, thereby alerting their absence to the owners or co-owners of cards for which they are a reviewer, co-reviewer, quality analyst or co-quality analyst.
-Local Timezone
+
+**Local Timezone**

 You can see your local timezone, if different from UTC. This will allow you to get the best out of the Daily Kanban Board. Just go to the My Timezone option on the User menu towards the top right.

Cards modified by Rebecca Shalfield

2019-10-28T21:25:44.765000Z

--- v6
+++ v7
@@ -1,4 +1,4 @@
-Cards
+**Cards**

 *     Context of a card's title retained due to grandparent and parent title also being displayed.
 *     Details of a particular card can be reached via unique URL based on card ID (i.e. Kanbanara-12345), thereby allowing a direct link.
@@ -16,7 +16,8 @@
 Details of a particular card can be reached via unique URL based on card ID (i.e. ABC-12345), thereby allowing direct link.

 A card changed in the last 24 hours will be shown slightly rotated on the kanban board to indicate the same.
-Card Types
+
+**Card Types**

 A card placed on the kanban board can be of any one of nine types:

@@ -132,7 +133,8 @@
 **Custom Attributes**

 Any number of user-defined custom attributes can be added to all cards in a particular project. Just define the custom attributes within the project itself and every time you add, update or view a card in that project, such custom attributes will appear and be editable.
-Card Menu
+
+**Card Menu**

 Each card on the kanban board posseses a popup menu that allows you to do the following:

@@ -162,49 +164,45 @@
 *     Transfer - Allows a card for which you are the owner to be moved from one project to any other in which you are a member. If the card was previously a member of this project, an attempt will be made to retain its previous ID.
 *     Continue [Only available in final state] - Allows a closed card to be continued in another project in which you are a member.

-Adding or Updating a Card
+**Adding or Updating a Card**

 If you have been invited onto a project as a guest, you will be able to view any card but can not add a new one or update an existing one.

 Unlike other project management systems, Kanbanara has no notion of a read only kanban board. The ‘editableby’ attribute to each card ensures only those allowed to do so can edit an individual card. The settings of the editableby attribute indicate which edit groups are able to edit an individual card. By default, each card will be assigned the following edit groups:

-    Creator - This edit group allows editing by the team member who created an individual card.
-
-    ProjectManagers - This edit group allows editing by the project manager or deputy project manager.
-
-    OwnerSelfAssignable - This edit group allow a team member to self-assign themselves as a card’s owner when such an unassigned card reaches an appropriate owner state. Just click on the ‘Assign To Me’ button within an individual card’s menu.
-
-    QualityAnalystSelfAssignable - This edit group allow a team member to self-assign themselves as a card’s quality analyst when such an unassigned card reaches a QA state. Just click on the ‘Assign To Me’ button within an individual card’s menu.
-
-    ReviewerSelfAssignable - This edit group allow a team member to self-assign themselves as a card’s reviewer when such an unassigned card reaches a review state. Just click on the ‘Assign To Me’ button within an individual card’s menu.
-
-    Owners - This edit group allows editing by the owner or co-owner.
-
-    QualityAnalysts - This edit group allows editing by the quality analyst or co-quality analyst.
-
-    Reviewers - This edit group allows editing by the reviewer or co-reviewer.
-
-    TeamMembers - This edit group allows editing by any team member except one invited as a guest.
+*     Creator - This edit group allows editing by the team member who created an individual card.
+*     ProjectManagers - This edit group allows editing by the project manager or deputy project manager.
+*     OwnerSelfAssignable - This edit group allow a team member to self-assign themselves as a card’s owner when such an unassigned card reaches an appropriate owner state. Just click on the ‘Assign To Me’ button within an individual card’s menu
+*     QualityAnalystSelfAssignable - This edit group allow a team member to self-assign themselves as a card’s quality analyst when such an unassigned card reaches a QA state. Just click on the ‘Assign To Me’ button within an individual card’s menu.
+*     ReviewerSelfAssignable - This edit group allow a team member to self-assign themselves as a card’s reviewer when such an unassigned card reaches a review state. Just click on the ‘Assign To Me’ button within an individual card’s menu.
+*     Owners - This edit group allows editing by the owner or co-owner.
+*     QualityAnalysts - This edit group allows editing by the quality analyst or co-quality analyst.
+*     Reviewers - This edit group allows editing by the reviewer or co-reviewer.
+*     TeamMembers - This edit group allows editing by any team member except one invited as a guest.

 At any time, you have the option to add or remove any of these edit groups from any card you are allowed to edit.
-Add Card
+
+**Add Card**

 The Add Card page allows you to add a card of type epic, feature, story, enhancement, defect, task, bug, test or transient to the Kanban board.

 Should you enter a fair amount of text into one of a number of textarea input fields, a text-to-speech facility is available to allow you to listen to your text prior to submission.
-Update Card
+
+**Update Card**

 The Update Card page allows you to edit any existing card regardless of its type.

 Should you enter a fair amount of text into one of a number of textarea input fields, a text-to-speech facility is available to allow you to listen to your text prior to submission.
-Delete Card
+
+**Delete Card**

 The Delete Card page is reached whenever you select an individual card for deletion by clicking on its Delete menu option.

 You will only be able to perform this action if the project’s ‘Allow Card Deletions’ setting has been enabled (disabled by default

 Please note that the deletion of a parent card will cause all its children to be deleted at the same time.
-Priorities and Severities
+
+**Priorities and Severities**

 Kanbanara supports both priority and severity, each to four levels, thus giving one of sixteen levels of urgency and importance to an individual card ranging from critical-critical, through high and medium, down to low-low.

@@ -220,7 +218,8 @@
 This is not strictly true for the Backlog column, where cards may be displayed in the order they have been arranged by via the Backlog Pyramid.

 Coupled with the assignment of a severity, this allows you to sort your cards into one of sixteen priority-severity pairs.
-Severities
+
+**Severities**

 A card will be assigned one of four severities - Critical, High, Medium or Low - at any given time, the default being Medium.

@@ -246,17 +245,12 @@

 An individual card can be blocked in one of several ways:

-    Explicitly blocked by one or more of its children.
-
-    Automatically blocked if the states of the parent and any one of its children are in conflict.
-
-    Explicitly blocked until manually unblocked.
-
-    Explicitly blocked until a set date when it will be automatically unblocked.
-
-    Blocked due to its state being ahead in the workflow than that of one or more of its prerequisites. The prerequisites (formerly ‘after’) attribute is the equivalent of a ‘Blocked By’ attribute which Kanbanara does not possess.
-
-    Blocked due to its state being ahead in the workflow than that of one or more of its facilitators. A facilitator is set in the facilitates attribute (formerly ‘before’) of another card.
+*     Explicitly blocked by one or more of its children.
+*     Automatically blocked if the states of the parent and any one of its children are in conflict.
+*     Explicitly blocked until manually unblocked.
+*     Explicitly blocked until a set date when it will be automatically unblocked.
+*     Blocked due to its state being ahead in the workflow than that of one or more of its prerequisites. The prerequisites (formerly ‘after’) attribute is the equivalent of a ‘Blocked By’ attribute which Kanbanara does not possess.
+*     Blocked due to its state being ahead in the workflow than that of one or more of its facilitators. A facilitator is set in the facilitates attribute (formerly ‘before’) of another card.

 **Next Action and Deadline**

Cards modified by Rebecca Shalfield

2019-10-28T21:21:10.019000Z

--- v5
+++ v6
@@ -1,12 +1,9 @@
 Cards

-    Context of a card?s title retained due to grandparent and parent title also being displayed.
-
-    Details of a particular card can be reached via unique URL based on card ID (i.e. Kanbanara-12345), thereby allowing a direct link.
-
-    Attachments can be made to a card.
-
-    Partial inline editing.
+*     Context of a card's title retained due to grandparent and parent title also being displayed.
+*     Details of a particular card can be reached via unique URL based on card ID (i.e. Kanbanara-12345), thereby allowing a direct link.
+*     Attachments can be made to a card.
+*     Partial inline editing.

 Such cards can be chained together with a simple parent-child relationship. Although a parent can have many children, a child can have only one parent. Placeholder

@@ -36,7 +33,8 @@
 All cards or just those of a particular type can be shown on the kanban board.

 Such cards can be hierarchically chained together with a simple parent-child relationship. Although a parent can have many children, a child can have only one parent.
-Card Attributes
+
+**Card Attributes**

 Many attributes can be assigned to each card:

@@ -138,55 +136,31 @@

 Each card on the kanban board posseses a popup menu that allows you to do the following:

-    View - Allows all the attributes of an individual card to be viewed.
-
-    Update - Allows an individual card to be updated.
-
-    Hierarchy
-
-    Execute Rules - Trigger all the rules associated with a particular card.
-
-    Give Focus - Declares that an individual card has your undivided attention.
-
-    Touch - Allows you to ‘touch’ a card thus indicating to others that you have not forgotten about it.
-
-    Poke - If you are the owner or coowner of a card which is in a review or QA state, this menu option allows you to poke the reviewers or quality analysts. The poke flag will be subsequently cancelled should the card be touched or updated or dragged and dropped upon a new state.
-
-    Add Substory - Allows a child sub-story to be added to a story card.
-
-    Add Task - Allows a child task to be added to a card.
-
-    Add Test - Allows a child test to be added to a card.
-
-    Add Defect - Allows a child defect to be added to a card.
-
-    Add Bug - Allows a child bug to be added to a card.
-
-    Attach - Allows you to upload and attach a file to an individual card.
-
-    Split Story - Allows you to split a story in half.
-
-    Internals - Allows you to display all the attributes of a card including the internal ones.
-
-    Delete - Allows you to delete an individual card (if project’s ‘Allow Card Deletions’ setting enabled).
-
-    JSON - Allows you to display all the attributes of a card in JSON format.
-
-    Expedite - Allows a card to be rendered expedited
-
-    Unexpedite - Allows the current expedited card for a project to be rendered unexpedited.
-
-    Top - Move card to top within those cards with same state, priority and type on kanban board.
-
-    Up - Move card up one within those cards with same state, priority and type on kanban board.
-
-    Down - Move card down one within those cards with same state, priority and type on kanban board.
-
-    Bottom - Move card to bottom within those cards with same state, priority and type on kanban board.
-
-    Transfer - Allows a card for which you are the owner to be moved from one project to any other in which you are a member. If the card was previously a member of this project, an attempt will be made to retain its previous ID.
-
-    Continue [Only available in final state] - Allows a closed card to be continued in another project in which you are a member.
+*     View - Allows all the attributes of an individual card to be viewed.
+*     Update - Allows an individual card to be updated.
+*     Hierarchy
+*     Execute Rules - Trigger all the rules associated with a particular card.
+*     Give Focus - Declares that an individual card has your undivided attention.
+*     Touch - Allows you to ‘touch’ a card thus indicating to others that you have not forgotten about it.
+*     Poke - If you are the owner or coowner of a card which is in a review or QA state, this menu option allows you to poke the reviewers or quality analysts. The poke flag will be subsequently cancelled should the card be touched or updated or dragged and dropped upon a new state.
+*     Add Substory - Allows a child sub-story to be added to a story card.
+*     Add Task - Allows a child task to be added to a card.
+*     Add Test - Allows a child test to be added to a card.
+*     Add Defect - Allows a child defect to be added to a card.
+*     Add Bug - Allows a child bug to be added to a card.
+*     Attach - Allows you to upload and attach a file to an individual card.
+*     Split Story - Allows you to split a story in half.
+*     Internals - Allows you to display all the attributes of a card including the internal ones.
+*     Delete - Allows you to delete an individual card (if project’s ‘Allow Card Deletions’ setting enabled).
+*     JSON - Allows you to display all the attributes of a card in JSON format.
+*     Expedite - Allows a card to be rendered expedited
+*     Unexpedite - Allows the current expedited card for a project to be rendered unexpedited.
+*     Top - Move card to top within those cards with same state, priority and type on kanban board.
+*     Up - Move card up one within those cards with same state, priority and type on kanban board.
+*     Down - Move card down one within those cards with same state, priority and type on kanban board.
+*     Bottom - Move card to bottom within those cards with same state, priority and type on kanban board.
+*     Transfer - Allows a card for which you are the owner to be moved from one project to any other in which you are a member. If the card was previously a member of this project, an attempt will be made to retain its previous ID.
+*     Continue [Only available in final state] - Allows a closed card to be continued in another project in which you are a member.

 Adding or Updating a Card

Cards modified by Rebecca Shalfield

2019-10-28T21:16:58.113000Z

--- v4
+++ v5
@@ -40,187 +40,98 @@

 Many attributes can be assigned to each card:

-    _id
-
-    Actual Cost
-
-    Actual Cost History
-
-    Actual Time
-
-    Actual Time History
-
-    Affects Version
-
-    Artifacts
-
-    Award
-
-    Blocked
-
-    Blocked Until
-
-    Blocks Parent
-
-    Broadcast
-
-    Bypass Review
-
-    Categories
-
-    Class of Service
-
-    Comments
-
-    Continued From
-
-    Continued In
-
-    Co-Owner
-
-    Co-Quality Analyst
-
-    Co-Reviewer
-
-    Creator
-
-    CRM Case
-
-    Customer
-
-    Deadline
-
-    Deferred
-
-    Deferred Until
-
-    Depends Upon
-
-    Description
-
-    Difficulty
-
-    Emotion
-
-    Escalation
-
-    Estimated Cost
-
-    Estimated Cost History
-
-    Estimated Time
-
-    Estimated Time History
-
-    Expedite
-
-    External Hyperlink
-
-    External Reference
-
-    Facilitates (formerly Before)
-
-    Fix Version
-
-    Focus History
-
-    Hashtags
-
-    HiddenUntil
-
-    Hierarchy
-
-    ID
-
-    Iteration
-
-    Last Changed
-
-    Last Changed By
-
-    Last Poked
-
-    Last Poked By
-
-    Last Touched
-
-    Last Touched By
-
-    MMRs (Minimum Marketable Releases)
-
-    Mode
-
-    Next Action
-
-    Notes
-
-    Owner
-
-    Parent
-
-    Prerequisites (formerly After) (This is the equivalent of a ‘Blocked By’ attribute which Kanbanara does not possess)
-
-    Priority
-
-    Project
-
-    Qualitative Urgency (One half of Qualitative Cost of Delay)
-
-    Qualitative Value (One half of Qualitative Cost of Delay)
-
-    Quality Analyst
-
-    Reassign Co-Owner
-
-    Reassign Co-Quality Analyst
-
-    Reassign Co-Reviewer
-
-    Reassign Owner
-
-    Reassign Quality Analyst
-
-    Reassign Reviewer
-
-    Recurring
-
-    Release
-
-    Resolution
-
-    Reviewer
-
-    Root Cause Analysis
-
-    Severity
-
-    Source
-
-    Start By
-
-    State
-
-    State History
-
-    Status
-
-    Stuck
-
-    Subteam
-
-    Tags
-
-    Test Cases
-
-    Title
-
-    Type
-
-    Unplanned
-
-    Votes
-
-Custom Attributes
+*     _id
+*     Actual Cost
+*     Actual Cost History
+*     Actual Time
+*     Actual Time History
+*     Affects Version
+*     Artifacts
+*     Award
+*     Blocked
+*     Blocked Until
+*     Blocks Parent
+*     Broadcast
+*     Bypass Review
+*     Categories
+*     Class of Service
+*     Comments
+*     Continued From
+*     Continued In
+*     Co-Owner
+*     Co-Quality Analyst
+*     Co-Reviewer
+*     Creator
+*     CRM Case
+*     Customer
+*     Deadline
+*     Deferred
+*     Deferred Until
+*     Depends Upon
+*     Description
+*     Difficulty
+*     Emotion
+*     Escalation
+*     Estimated Cost
+*     Estimated Cost History
+*     Estimated Time
+*     Estimated Time History
+*     Expedite
+*     External Hyperlink
+*     External Reference
+*     Facilitates (formerly Before)
+*     Fix Version
+*     Focus History
+*     Hashtags
+*     HiddenUntil
+*     Hierarchy
+*     ID
+*     Iteration
+*     Last Changed
+*     Last Changed By
+*     Last Poked
+*     Last Poked By
+*     Last Touched
+*     Last Touched By
+*     MMRs (Minimum Marketable Releases)
+*     Mode
+*     Next Action
+*     Notes
+*     Owner
+*     Parent
+*     Prerequisites (formerly After) (This is the equivalent of a ‘Blocked By’ attribute which Kanbanara does not possess)
+*     Priority
+*     Project
+*     Qualitative Urgency (One half of Qualitative Cost of Delay)
+*     Qualitative Value (One half of Qualitative Cost of Delay)
+*     Quality Analyst
+*     Reassign Co-Owner
+*     Reassign Co-Quality Analyst
+*     Reassign Co-Reviewer
+*     Reassign Owner
+*     Reassign Quality Analyst
+*     Reassign Reviewer
+*     Recurring
+*     Release
+*     Resolution
+*     Reviewer
+*     Root Cause Analysis
+*     Severity
+*     Source
+*     Start By
+*     State
+*     State History
+*     Status
+*     Stuck
+*     Subteam
+*     Tags
+*     Test Cases
+*     Title
+*     Type
+*     Unplanned
+*     Votes
+
+**Custom Attributes**

 Any number of user-defined custom attributes can be added to all cards in a particular project. Just define the custom attributes within the project itself and every time you add, update or view a card in that project, such custom attributes will appear and be editable.
 Card Menu