This is a brief description of writing Jira stories for the Folijet development team. This assumes the Product Owner is writing UI stories, which may then be supplemented by, or changed into, backend (MOD) stories by the developers once they review and refine them.
Top part of the Jira
- In the Jira menu bar, to the left of the search box, click on "Create"
- It will usually show a screen with the most recent project and issue type that you have been working on
- Project:
- UIDATIMP for Data Import stories (usually used for the Data Import landing page, log page, and settings)
- UIIN for Inventory stories (note that a number of stories related to Data Import features may actually be UIIN stories, if they affect screens in Inventory rather than Data Import)
- Type: Story
- Status:
- Open, if all the details are there
- Draft, if you need to add more to it before it's ready for the developers
- Priority
- P3 for regular priority
- P2 for higher priority
- Rarely you will use P1 for highest priority or P4 for low priority
- Resolution: Ignore
- Affects versions: Ignore
- Fix versions: Ignore - developer will add before release
- Labels
- epam-folijet: add to every Folijet Jira issue
- inventory: add to any Jira issue dealing with the Inventory app, screens, or settings
- data-import: add to any Jira issue dealing with the Data Import app, screens, or settings
- Note that some issues may have both the inventory and data-import labels on them (e.g. find one)
- ecs: add to any Jira issue related to enhanced consortial support
- folijet-refinement: add to any Jira issue that does not have points. Remove once the issue has been pointed
- needs-points: add to any Jira issue that does not have points. Remove once the issue has been pointed
- next-refinement: add to any Jira issue that you want to review with the developers at the next refinement session. Some issues may have the label folijet-refinement, but they will not be reviewed until the additional label next-refinement is added. Remove once the issue has been pointed
- needs-testrail: add to any Jira story covering new functionality. Once the manual QA has written the Jira, they will change it to has-testrail
- Template: Ignore
- Sprint: Ignore - scrum master will add
- Story points: Ignore - developers will add
- Development team: Folijet
- Release: (Flower release that the story belongs to)
- Epic link: (Epic that the story belongs to, usually...)
- Batch manager (UXPROD-47, for Data Import)
- Inventory (UXPROD-75, for Inventory)
- Enhanced consortial support (UXPROD, for Consortia)
Description
Links
Next steps
Sample Stories