• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently my team and a number of others I know list Acceptance criteria" for story by creating a list in the description field of the JIRA. This is too freeform and non exact.

      One of the sub-tasks for the story would typically be to feature test the story for all the acceptance criteria in the list.

      It would be more ideal if were possible to build a list of Acceptance Criteria for a story which would show under the story similarly to sub tasks. Each acceptance criteria could have a checkbox to indicate it was tested and on what date and any comments.

            [JSWSERVER-7754] Add "Acceptance criteria" list to GreenHopper story

            Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time. Regards, JIRA Agile Team

            @Whyves – This is not possible in the OnDemand version.

            Nicholas Crown added a comment - @Whyves – This is not possible in the OnDemand version.

            @Tom

            Custom fields are an integral part of JIRA. Atlassian already has the Multi Checkboxes Custom Fields. Checklist is roughly based on it and uses the same mechanisms but it adds more features. At the end of the day, if Atlassian was to "integrate" Checklist, they would implement it as a custom field either.

            Yves Riel [Okapya] added a comment - @Tom Custom fields are an integral part of JIRA. Atlassian already has the Multi Checkboxes Custom Fields. Checklist is roughly based on it and uses the same mechanisms but it adds more features. At the end of the day, if Atlassian was to "integrate" Checklist, they would implement it as a custom field either.

            boardtc added a comment - - edited

            @Whyves, this looks real ideal, thanks.

            Here is the vendor's help page http://www.okapya.com/jira-agile-definition-of-done-acceptance-criteria

            I am reluctant to start using another plugin with custom fields when this should be built in functionality. Atlassian should buy Okapya!

            boardtc added a comment - - edited @Whyves, this looks real ideal, thanks. Here is the vendor's help page http://www.okapya.com/jira-agile-definition-of-done-acceptance-criteria I am reluctant to start using another plugin with custom fields when this should be built in functionality. Atlassian should buy Okapya!

            You way want to take a look at this JIRA add-on: Checklist.

            It is a custom field that can be added to any issue type (e.g. Story). You can also use a workflow validator to prevent the transition of the issue until the acceptance criteria have been checked. It will display the criteria in a checkbox form.

            Yves Riel [Okapya] added a comment - You way want to take a look at this JIRA add-on: Checklist . It is a custom field that can be added to any issue type (e.g. Story). You can also use a workflow validator to prevent the transition of the issue until the acceptance criteria have been checked. It will display the criteria in a checkbox form.

            This would be incredibly useful to better organizing the criteria as a "first-class citizen", so to speak. We need to be able to record the status for each acceptance criteria. A simple checkbox would be nice (see JRA-3374) for 95% of projects.

            If the acceptance criteria were sub-tasks behind the scenes, then we could even record status on the each criteria. For example, criteria could transition, if necessary for the project, from a status of 'developed' to 'accepted'.

            The main point of having separate items for each acceptance criteria is (1) to provide a functional status on a story and (2) to log the acceptance of each passing criteria by a responsible stakeholder. The one-to-many nature of a user story to acceptance criteria is not well represented in a free-form text box. As-is, this seems to be something of an unpolished afterthought.

            Jonathan Boarman added a comment - This would be incredibly useful to better organizing the criteria as a "first-class citizen", so to speak. We need to be able to record the status for each acceptance criteria. A simple checkbox would be nice (see JRA-3374 ) for 95% of projects. If the acceptance criteria were sub-tasks behind the scenes, then we could even record status on the each criteria. For example, criteria could transition, if necessary for the project, from a status of 'developed' to 'accepted'. The main point of having separate items for each acceptance criteria is (1) to provide a functional status on a story and (2) to log the acceptance of each passing criteria by a responsible stakeholder. The one-to-many nature of a user story to acceptance criteria is not well represented in a free-form text box. As-is, this seems to be something of an unpolished afterthought.

              Unassigned Unassigned
              bb404b8a30d3 boardtc
              Votes:
              13 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: