Commit 3e5d5add authored by Sid Sijbrandij's avatar Sid Sijbrandij

Fix links to priority.

parent 033a27bd
......@@ -235,14 +235,12 @@ out to any of the other C-level team members or our board member Bruce Armstrong
1. Give the community the **chance to help**. For example: place issues on the feedback tracker, leave comments in rake check tests about what you can run manually and ask 'Can you send a merge request to fix this?'.
1. Submit the **smallest** item of work that makes sense. When creating an issue describe the smallest fix possible, put suggestions for enhancements in separate issues and link them. If you're new to GitLab and are writing documentation or instructions submit your first merge request for at most 20 lines.
1. Do not leave issues open for a long time, issues should be **actionable** and realistic. If you are assigned but don't have time, assign it to someone else. If nobody is assigned and it is not a priority, please ensure the community can help and close it.
1. Make a conscious effort to **prioritize**<a href="prioritize"></a> your work. The priority of items depends on multiple factors: is there a team member waiting for the answer, what is the impact if you delay it, how many people does it affect, etc.
The priority starting from urgent is:
1. Make a conscious effort to **prioritize**<a name="prioritize"></a> your work. The priority of items depends on multiple factors: is there a team member waiting for the answer, what is the impact if you delay it, how many people does it affect, etc. The priority starting from urgent is:
1. @mentions from team members and the rest of the community
1. Issues assigned to the upcoming milestone
1. Issues assigned to future milestones
1. Issues not assigned to a milestone
In the same milestone the priority starting from urgent is:
1. Within the same milestone the priority<a name="prioritize"></a> starting from urgent is:
1. **Emergency** issues (a service engineer will probably contact you via chat)
1. [**Security**](https://gitlab.com/groups/gitlab-org/issues?milestone_title=8.7&label_name=security) issues
1. [**Data integrity**](https://gitlab.com/groups/gitlab-org/issues?milestone_title=8.7&label_name=data+integrity) issues (preventing data loss)
......
......@@ -54,6 +54,6 @@ Check out our [remote manifesto](https://about.gitlab.com/2015/04/08/the-remote-
You work on issues tagged with 'Developer' on [CE](https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name=Developer) and [EE](https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name=Developer).
Some issues might be missing any [workflow label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md#workflow-labels) but be ready for a developer, in this case feel free to add a 'Developer' label.
The priority of the issues tagged with this label can be found in [the handbook under GitLab Workflow](https://about.gitlab.com/handbook/#prioritize).
The priority of the issues tagged with this label can be found in [the handbook under GitLab Workflow under prioritize](https://about.gitlab.com/handbook/#prioritize) and [priority in the same milestone](https://about.gitlab.com/handbook/#priority).
When done with an issue remove the 'Developer' label and add the next [workflow label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md#workflow-labels) or create a merge request and assign it someone that has 'Merge request endboss' on their [team page](https://about.gitlab.com/team/) listing.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment