quality-time icon indicating copy to clipboard operation
quality-time copied to clipboard

Synchronize the status of technical debt and the status of issues

Open fniessink opened this issue 3 years ago • 0 comments

Epic

As a quality manager, I want the status of technical debt in Quality-time and the status of issues in the issue tracker to be synchronized so I don't have to manage technical debt status in two different tools.

Acceptance criteria

  • [x] Resolving the issues in the issue tracker ignores the technical debt accepted in Quality-time
  • [x] Creating an issue adds the issue id to the tracked issue ids.
  • [ ] Creating an issue automatically accepts technical debt if the user explicitly selects "Create issue and accept technical debt"
  • [ ] Accepting technical debt creates one or more related issues in the issue tracker

Assumptions

  • An issue tracker has been configured.

Open issues

  • Automatically doing something when the user makes a change can be confusing (e.g. automatically creating an issue if the user accepts technical debt). How to prevent confusion?
  • Make the create issue button a dropdown button with two options: "create issue" and "create issue and accept technical debt"?
  • As a quality manager I want to accept technical debt, set the technical debt target, and (optionally) create an issue in one user action (UI: change the accept debt yes/no dropdown into a button with dropdown and options: 1. accept debt 2. accept debt and set debt target to current measurement value, 3. accept debt and set debt target to current measurement value and create issue 4. unaccept technical debt)

Out of scope

  • Notifiying the user that the technical debt of a metric was "unaccepted" because the last issue was resolved.
  • Configurability
  • Technical debt can have an end date at the moment, syncing that end date with the due date of issues is out of scope.

Rejected functionality

  • Automatically creating a new issue when the user accepts technical debt. Doing this automatically may be too surprising and/or annoying.

User stories

Essential for the epic

  • #2931
  • #3935
  • #4493

Not essential for the epic

  • #4232
  • #4494
  • #4614
  • #4747

Related

  • #4074
  • #4165
  • #4185
  • #4186

Other info

Discussed in https://github.com/ICTU/quality-time/discussions/3993, originally posted by Sebastiaan127001 June 8, 2022.

fniessink avatar Jun 09 '22 07:06 fniessink