Streamline entering in SP estimates for complex JIRA issues

[comps]

When estimating epics / tasks / subtasks, we usually

1. copy/paste the issues (links with subjects) to a shared word document
2. go through it one-by-one on a meeting
3. agree on min/avg/max or at least we each say our own estimate and write down the approx. average of them
4. task one person to go through the unpleasant process of entering it into estimagus

This could probably be improved by estimagus offering a user-friendly interface to streamline this process, such as:

• one page representing the subject of estimation (epic, task) with its child items inlined on the page as table-ish rows
• each row would contain
  • ID of the child item (hyperlinking to JIRA)
  • its subject (header/summary)
  • current estimated SP (if entered previously, or if somebody was proactive in JIRA)
  • 3 fields for min/avg/max
• (ideally) entered values would be temporarily stored as a cookie, so we don't lose estimation-in-progress if a laptop battery dies or if estimagus fails to submit due to some outage
• there would be one button at the bottom to submit everything

This would ideally require no token input (if it would be internal to estimagus), but if this is not possible, then an input field for token would be right above / next to the submit button.

---

The above is really meant as a problem description, not a description of an implementation - I used implementation examples to hopefully describe the problem better.

[matejak]

Recent enhancements to Estimagus enabled progress on this issue. Has the solution become more obvious in the meantime? Implementation-wise, it is 90% an HTML exercise that doesn't affect Estimagus backend significantly, which means that it can be prototyped in a relatively flexible way with realistic ETA later in 2024.