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
Our current comment checking rule requires a comment if:
time has been logged AND the issue isn't closed
OR the issue is in progress
A conceptually simpler rule is to require a comment whenever time has been logged. i.e a comment must be added "around" the same time that a worklog is added.
The check would look at:
time of most recent worklog
time of most recent comment
the rule would pass if the comment was <1d before the worklog or after it.
What makes it non-trivial is that worklogs and comments are both paginated fields, so they may be truncated. Issues are currently retrieved using the search API. We need to do one of:
see if those fields can be sorted so that we always get the most recent comment and worklog
check search results and (if necessary) pull individual ticket comments and worklogs
The text was updated successfully, but these errors were encountered:
Our current comment checking rule requires a comment if:
A conceptually simpler rule is to require a comment whenever time has been logged. i.e a comment must be added "around" the same time that a worklog is added.
The check would look at:
the rule would pass if the comment was <1d before the worklog or after it.
What makes it non-trivial is that worklogs and comments are both paginated fields, so they may be truncated. Issues are currently retrieved using the search API. We need to do one of:
The text was updated successfully, but these errors were encountered: