Can you add filters to JIRA about labels ? #8696
-
|
Hi, we have a setup in Jira that one team is working on different products, but use the same sprint board. Issues can be distinguished by labels to which product they belong. Is it possible to use the JIRA connection and add filters to the connection, so that I can set up the different products in DevLake, but receive the right issues from JIRA. Simply providing the board would pollute the data. Or is there another option to differentiate the different products for a team sprint board in JIRA ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Yes, you can filter JIRA issues by labels in DevLake, but not directly in the DevLake connection setup. Instead, you need to customize the JQL filter for your JIRA board to include label-based criteria (for example, Currently, DevLake does not support configuring label-based filters directly in its UI or connection settings. As an alternative, you can differentiate products post-ingestion by using labels in your queries or dashboards. There is also a proposed (but not yet implemented) feature to use custom Lua scripts for more advanced label-based mapping after ingestion (source). To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Yes, you can filter JIRA issues by labels in DevLake, but not directly in the DevLake connection setup. Instead, you need to customize the JQL filter for your JIRA board to include label-based criteria (for example,
labels = productA). DevLake will then respect this filter and only ingest issues matching the JQL when collecting data from that board. If you update the board's JQL filter, you may need to trigger a full sync in DevLake to refresh the data—this can be done by setting the environment variableJIRA_JQL_AUTO_FULL_REFRESH=trueor via the UI. This approach lets you set up different products in DevLake and receive only the relevant issues for each, avoiding data pollution from unr…