This repository has been archived by the owner on May 2, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
Workflow Agile Development
hundehausen edited this page Mar 15, 2021
·
5 revisions
- Look for a ticket in Jira from the backlog
- Tickets with higher priority are considered to be chosen first
- Assign ticket to yourself and move it to
in progress
- Create new branch from
develop
branch for smaller tasks (hotfix, bugfix, story, subtask) or usemaster
branch for epics- Naming:
feature/<ticket-no.>-description
orhotfix/<ticket-no.>-<description>
- For example:
feature/1234-fixing_style_upload_button
- The No. of the feature branch is always from the "highest" ticket-layer like epic -> story -> subtask
- The same number and name is used for different repositories (frontend / backend) if it is the same task
- Naming:
- Write code, test it properly
- Commit your changes, comment in the ticket, add the URL to the merge request and move it to
Dev Approval
- Commit messages on the other hand have the smallest ticket no. like from a subtask for example
- Example:
[TIPXMR-2345] <description>
- Don't loose track of your ticket, keep an eye on it until it is merged and done
- If your branch gets merged, please delete the branch
- The master branch is always working, no unfinished features are merged into it
- Work on a dev approval before you start a new story
- Changes that differ from the ticket description must be documented in the ticket and commit message
- If new tasks arise, wirte a ticket and save it to the backlog
- A ticket has fields like prioriry, frontend or backend