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: plugins/jira-dashboard/README.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,6 +184,27 @@ metadata:
184
184
jira.com/incoming-issues-status: Incoming # The name of the status for incoming issues in Jira. Default: New
185
185
```
186
186
187
+
#### Custom JQL Annotation
188
+
189
+
You can use the `jira.com/jql` annotation to specify a custom [Jira Query Language (JQL)](https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql/) query for your entity.
190
+
**When this annotation is present, it will override the values set by `jira.com/components`, and `jira.com/filter-ids`.**
191
+
This allows you to fully customize which issues are shown in the Jira Dashboard for your entity.
192
+
193
+
**Example:**
194
+
195
+
```yaml
196
+
apiVersion: backstage.io/v1alpha1
197
+
kind: Component
198
+
metadata:
199
+
annotations:
200
+
jira.com/jql: component = OurProject AND Affected = 1.1
201
+
```
202
+
203
+
**Note:**
204
+
205
+
- Make sure your JQL is valid and returns the issues you expect.
206
+
- If you use `jira.com/jql`, you do not need to set `jira.com/components`, or `jira.com/filter-ids` for that entity. However, you still need to specify the `jira.com/project-key` annotation.
207
+
187
208
### New Frontend System (Alpha)
188
209
189
210
The Jira Dashboard plugin also has support for the [new alpha frontend system](https://backstage.io/docs/frontend-system/). Here is how you can set it up:
0 commit comments