You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: patterns/2-structured/project-setup/issue-tracker.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,27 +1,27 @@
1
-
# Title
1
+
##Title
2
2
3
3
Issue tracker use cases
4
4
5
-
# Patlet
5
+
##Patlet
6
6
7
7
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.
8
8
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
17
10
18
11
A team develops a component that many teams in the organization depend on. It
19
12
uses a standard issue tracker for tracking open bugs and feature requests.
20
13
However the context in each entry is very limited. As a result potential
21
14
contributors have no way of knowing what change exactly each issue is talking
22
15
about.
23
16
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
25
25
26
26
- Contributors would like to understand whether the feature that they are
27
27
missing is already on the roadmap. With a lot of context missing in issues
@@ -38,7 +38,7 @@ about.
38
38
component becomes an exercise in project archaeology and brain picking of people
39
39
who remember what was discussed.
40
40
41
-
# Solution
41
+
##Solution
42
42
43
43
Embrace the "written over verbal" philosophy not only for pure software
44
44
development but also during the planning phase of new features:
@@ -64,7 +64,7 @@ development but also during the planning phase of new features:
64
64
include hints about what kind of information is needed for the other usage
65
65
types.
66
66
67
-
# Resulting Context
67
+
##Resulting Context
68
68
69
69
- Making more use of the project's issue tracker for communication enables
70
70
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:
83
83
the ways of the project long before they have the first need to get involved.
0 commit comments