Skip to content

Commit ce9a2da

Browse files
h13i32marugitbook-bot
authored andcommitted
GitBook: [#229] No subject
1 parent 1c9ece3 commit ce9a2da

File tree

4 files changed

+32
-29
lines changed

4 files changed

+32
-29
lines changed
Loading
Loading

quick-start/basic-usage.md

+5-1
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,18 @@ description: >-
1010

1111
After setup, it will automatically create Streams.
1212

13-
![](../.gitbook/assets/initial-streams.png)
13+
![](<../.gitbook/assets/スクリーンショット 2022-08-16 19.18.59.png>)
1414

1515
| Stream | description |
1616
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
1717
| `Me` | <p>You can see the issues/pull requests that are relevant to you. Basically, you can look at this stream and you won't miss anything. <br>You will also see issues filtered by <code>My Issues</code>, <code>My PRs</code> and <code>Assign</code>.</p> |
1818
| `Team` | <p>Issues that are maintained by the team you are on.<br>You will also see issues filtered by team.</p> |
1919
| `Repo` | <p>Issues from the repositories you have recently been active in.<br>You can also see a filtered issues for each repository.</p> |
2020

21+
In addition, the following notice will appear after a while. Follow the instructions to create other streams.
22+
23+
![](<../.gitbook/assets/スクリーンショット 2022-08-16 19.19.49.png>)
24+
2125
## issues
2226

2327
![](../.gitbook/assets/03\_issues.png)

usecase/advanced.md

+27-28
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@ description: Integration with GitHub's features allows for more advanced usage.
44

55
# Advanced settings
66

7-
## Smartphone integration <a id="mobile"></a>
7+
## Smartphone integration <a href="#mobile" id="mobile"></a>
88

99
You must enable GitHub Notification Sync in order for Jasper to read issues viewed on a smartphone or normal browser.
1010

11-
![](../.gitbook/assets/07_notification_sync.png)
11+
![](../.gitbook/assets/07\_notification\_sync.png)
1212

13-
By enabling this setting, [GitHub Notifications](https://github.com/notifications) will periodically \(usually at 60-second intervals\) reflect this to Jasper.
13+
By enabling this setting, [GitHub Notifications](https://github.com/notifications) will periodically (usually at 60-second intervals) reflect this to Jasper.
1414

1515
{% hint style="warning" %}
1616
Jasper will only reflect the issue in GitHub Notifications if you have "Viewed and marked the issue as read". The following operations will not be reflected in GitHub Notifications
@@ -19,85 +19,85 @@ Jasper will only reflect the issue in GitHub Notifications if you have "Viewed a
1919
* Issues read using a menu or keyboard shortcut in Jasper
2020
{% endhint %}
2121

22-
## GitHub Projects Integration <a id="project"></a>
22+
## GitHub Projects Integration <a href="#project" id="project"></a>
2323

2424
To view issues related to a specific Github Project, create a Project Stream.
2525

2626
{% tabs %}
2727
{% tab title="Creating a Project Stream" %}
28-
![](../.gitbook/assets/07_project_stream1.png)
28+
![](../.gitbook/assets/07\_project\_stream1.png)
2929
{% endtab %}
3030

3131
{% tab title="View Project Stream" %}
32-
![](../.gitbook/assets/07_project_stream2.png)
32+
![](../.gitbook/assets/07\_project\_stream2.png)
3333
{% endtab %}
3434
{% endtabs %}
3535

3636
{% hint style="info" %}
37-
With the `project:REPOSITORY/PROJECT_BOARD` query, you can still create a regular Stream to view issues related to GitHub Projects. However, we recommend using Project Stream as it allows you to work with the Project Board \(Kanban\).
37+
With the `project:REPOSITORY/PROJECT_BOARD` query, you can still create a regular Stream to view issues related to GitHub Projects. However, we recommend using Project Stream as it allows you to work with the Project Board (Kanban).
3838
{% endhint %}
3939

40-
## GitHub Team Integration <a id="team"></a>
40+
## GitHub Team Integration <a href="#team" id="team"></a>
4141

4242
Use the Team Stream to view issues that have been mentioned to your GitHub Team.
4343

4444
{% tabs %}
4545
{% tab title="Enable Team Stream" %}
46-
![](../.gitbook/assets/07_team_stream1.png)
46+
![](../.gitbook/assets/07\_team\_stream1.png)
4747
{% endtab %}
4848

4949
{% tab title="Team Stream" %}
50-
![](../.gitbook/assets/07_team_stream3.png)
50+
![](../.gitbook/assets/07\_team\_stream3.png)
5151
{% endtab %}
5252

5353
{% tab title="Team Stream queries" %}
5454
Queries are automatically created from the Team you belong to.
5555

56-
![](../.gitbook/assets/07_team_stream2%20%281%29.png)
56+
![](../.gitbook/assets/07\_team\_stream2.png)
5757
{% endtab %}
5858
{% endtabs %}
5959

60-
## GitHub Watching Integration <a id="watching"></a>
60+
## GitHub Watching Integration <a href="#watching" id="watching"></a>
6161

6262
You can use the Watching Stream to view issues in repositories that you have watched on GitHub.
6363

6464
{% tabs %}
6565
{% tab title="Enable Watching Stream" %}
66-
![](../.gitbook/assets/07_watchiing_stream1.png)
66+
![](../.gitbook/assets/07\_watchiing\_stream1.png)
6767
{% endtab %}
6868

6969
{% tab title="Watching Stream" %}
70-
![](../.gitbook/assets/07_watching_stream2.png)
70+
![](../.gitbook/assets/07\_watching\_stream2.png)
7171
{% endtab %}
7272

7373
{% tab title="Watching Stream queries" %}
7474
Queries are automatically created from the repositories you watch.
7575

76-
![](../.gitbook/assets/07_watching_stream3.png)
76+
![](../.gitbook/assets/07\_watching\_stream3.png)
7777
{% endtab %}
7878
{% endtabs %}
7979

80-
## Register any issues <a id="subscription"></a>
80+
## Register any issues <a href="#subscription" id="subscription"></a>
8181

8282
If you want the issue to be a Stream on its own, rather than a repository or organization, use the Subscription Stream, which you enable from the configuration screen.
8383

8484
{% tabs %}
8585
{% tab title="Enable Subscription Stream" %}
86-
![](../.gitbook/assets/07_subscription_stream1.png)
86+
![](../.gitbook/assets/07\_subscription\_stream1.png)
8787
{% endtab %}
8888

8989
{% tab title="Subscription Stream" %}
90-
![](../.gitbook/assets/07_subscription_stream2.png)
90+
![](../.gitbook/assets/07\_subscription\_stream2.png)
9191
{% endtab %}
9292

9393
{% tab title="Register issue" %}
9494
Right-click on the Subscription Stream and register the URL of the issue in the menu.
9595

96-
![](../.gitbook/assets/07_subscription_stream3.png)
96+
![](../.gitbook/assets/07\_subscription\_stream3.png)
9797
{% endtab %}
9898
{% endtabs %}
9999

100-
## Optimizing the update interval <a id="optimize"></a>
100+
## Optimizing the update interval <a href="#optimize" id="optimize"></a>
101101

102102
Jasper typically looks for an issue every 10 seconds to get an update. This update interval is not per Stream, but rather for the entire Jasper. This means that the more Streams you create, the slower the update per Stream will be. For example, if you are creating three Streams, a Stream will only be updated every 30 seconds.
103103

@@ -115,33 +115,32 @@ For example, instead of creating two Streams, create a Stream and two Filter Str
115115

116116
{% tabs %}
117117
{% tab title="Two Streams" %}
118-
```text
118+
```
119119
org:nodejs
120120
```
121121

122-
```text
122+
```
123123
org:electron
124124
```
125125

126-
![](../.gitbook/assets/07_optimize_interval1.png)
126+
![](../.gitbook/assets/07\_optimize\_interval1.png)
127127
{% endtab %}
128128

129129
{% tab title="A Stream and two Filter Streams" %}
130-
```text
130+
```
131131
org:nodejs org:electron
132132
```
133133

134-
```text
134+
```
135135
org:nodejs
136136
```
137137

138-
```text
138+
```
139139
org:electron
140140
```
141141

142-
![](../.gitbook/assets/07_optimize_interval2.png)
142+
![](../.gitbook/assets/07\_optimize\_interval2.png)
143143
{% endtab %}
144144
{% endtabs %}
145145

146146
Jasper recommends using Filter Stream actively in this way.
147-

0 commit comments

Comments
 (0)