Skip to content

Commit e4c0ead

Browse files
committed
Fixes for the Issue Tracker pattern. fixes headline; changes order of sections; adapts status.
1 parent 87fd407 commit e4c0ead

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

patterns/2-structured/project-setup/issue-tracker.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,27 @@
1-
# Title
1+
## Title
22

33
Issue tracker use cases
44

5-
# Patlet
5+
## Patlet
66

77
The InnerSource host team fails to make not only plans and progress but also context for changes transparent. This is solved by increasing the use cases for the project issue tracker to also serve brainstorming, implementation discussion, and feature design.
88

9-
# Context
10-
11-
The InnerSource project tooling is all setup. However the project issue tracker
12-
is mainly used for sharing progress. In InnerSource projects there are many more
13-
use cases that an issue tracker can be used for that make remote, asynchronous
14-
communication easier.
15-
16-
# Problem
9+
## Problem
1710

1811
A team develops a component that many teams in the organization depend on. It
1912
uses a standard issue tracker for tracking open bugs and feature requests.
2013
However the context in each entry is very limited. As a result potential
2114
contributors have no way of knowing what change exactly each issue is talking
2215
about.
2316

24-
# Forces
17+
## Context
18+
19+
The InnerSource project tooling is all setup. However the project issue tracker
20+
is mainly used for sharing progress. In InnerSource projects there are many more
21+
use cases that an issue tracker can be used for that make remote, asynchronous
22+
communication easier.
23+
24+
## Forces
2525

2626
- Contributors would like to understand whether the feature that they are
2727
missing is already on the roadmap. With a lot of context missing in issues
@@ -38,7 +38,7 @@ about.
3838
component becomes an exercise in project archaeology and brain picking of people
3939
who remember what was discussed.
4040

41-
# Solution
41+
## Solution
4242

4343
Embrace the "written over verbal" philosophy not only for pure software
4444
development but also during the planning phase of new features:
@@ -64,7 +64,7 @@ development but also during the planning phase of new features:
6464
include hints about what kind of information is needed for the other usage
6565
types.
6666

67-
# Resulting Context
67+
## Resulting Context
6868

6969
- Making more use of the project's issue tracker for communication enables
7070
external contributors to follow along and make better decisions on what to
@@ -83,10 +83,10 @@ development but also during the planning phase of new features:
8383
the ways of the project long before they have the first need to get involved.
8484

8585

86-
# Known Instances
86+
## Known Instances
8787

8888
* Europace AG
8989

90-
# Status
90+
## Status
9191

92-
Proven
92+
Structured

0 commit comments

Comments
 (0)