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
Hi,
In order to get Change Failure Rate and Median Time to Restore Service metrics, looks like Apache DevLake can leverage Jira connector however it only connects to Jira Board, so it will collect [System] Incidents from the board of the project. Is there a way to allow DevLake to connect on Jira Projects instead of a Jira Boards ? (because have a board doesn't make sense in our scenario)
The text was updated successfully, but these errors were encountered:
Hi @danielrosa-zh, I'm here to help you with any bugs, questions, or contributions you have. Let me know how I can assist you!
I found a similar discussion that might address your question. In the discussion titled "Why are boards instead of jira projects selectable in a jira data scope?," it was explained that boards are used because sprints are bound to boards, which is essential for some metrics. Additionally, boards have filters, giving users control over what data is synced. This might be why the current setup is focused on boards rather than projects [1].
Question
Hi,
In order to get Change Failure Rate and Median Time to Restore Service metrics, looks like Apache DevLake can leverage Jira connector however it only connects to Jira Board, so it will collect [System] Incidents from the board of the project. Is there a way to allow DevLake to connect on Jira Projects instead of a Jira Boards ? (because have a board doesn't make sense in our scenario)
The text was updated successfully, but these errors were encountered: