[BUILD-660] Provide an easy-to-read breakdown of activity on open tickets Created: 24/Jan/22 Updated: 03/Mar/23 |
|
| Status: | Selected |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoR: |
Empty
|
||||||||||||
| Epic Link: | Release automation | ||||||||||||
| Team: | |||||||||||||
| Description |
|
The most critical activity in preflight checks is taking a look at tickets' activity:
However, all of this data is hard to fit in the current format, which is one line of text for all tickets. The goal of this ticket is to gather this data in a DB table and to present it conveniently at the end of preflight checks. |