Convert User Stories into Project Issues #76

New issue

Closed

opened 2025-05-05 10:17:41 +10:00 by Kruziikrel13 · 3 comments

Kruziikrel13 commented

2025-05-05 10:17:41 +10:00

(Migrated from github.com)

Using the user stories doc

Convert all stories into issues.

Note: User Stories will have labels and be in separate view to Planning board to prevent verbosity.

Using the [user stories doc](https://connectqutedu-my.sharepoint.com/:w:/r/personal/n8429693_qut_edu_au/_layouts/15/Doc.aspx?sourcedoc=%7BCF51FFC6-C4D4-4597-A14B-AF7A049C7500%7D&file=User%20Stories.docx&action=default&mobileredirect=true) Convert all stories into issues. - Note: User Stories will have labels and be in separate view to Planning board to prevent verbosity.

Kruziikrel13 commented

2025-07-25 13:07:41 +10:00

(Migrated from github.com)

This can't be completed until we actually have user stories... Tracked in #56

Kruziikrel13 commented

2025-08-03 17:08:22 +10:00

(Migrated from github.com)

In a slight change of plans we're going to use User stories as epics for which we then create our subset of project issues / tasks.

It'll be easier to generate our issues following the requirements spec where each issue can be defined as fulfilling whole or part of a requirement, and sets of requirements fulfill user stories (our epics)

In a slight change of plans we're going to use User stories as epics for which we then create our subset of project issues / tasks. It'll be easier to generate our issues following the requirements spec where each issue can be defined as fulfilling whole or part of a requirement, and sets of requirements fulfill user stories (our epics)

Kruziikrel13 commented

2025-09-15 18:56:24 +10:00

(Migrated from github.com)

Not planned, we are going to create a very basic set of user stories at the end of the project instead.

Note: this is not the proper to do things, but this is how we'll do in this specific set of circumstances.

Not planned, we are going to create a very basic set of user stories at the end of the project instead. Note: this is not the proper to do things, but this is how we'll do in this specific set of circumstances.

Commenting is not possible because the repository is archived.