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
#59 This may be the fix you're looking for. Take a look. Once the pull request is approved, you can put BlockedAttributes: Impediment into you config.yaml Criteria section and it should work. I would appreciate someone testing this out though.
@ActionableAgile@dvacanti any chance that this gets somehow into the data extractor code? It can hugely help to add the Blocked Days into the input for the Flow Efficiency graph. Queuing stages work well once you have identified possible bottlenecks, but having the Flag in JIRA reflected could uncover new queuing stages to look into.
In its current state, the tool does not calculate blocked days for items that are "Flagged" in JIRA as "Impediment".
The text was updated successfully, but these errors were encountered: