forcedotcom / forcedotcom/devops-center-feedback

Link or Clone work items? Reworking is inefficient (Work Item fails to pass UAT)

Open
#60 5 comments 32 reactions 0 assignees View on GitHub
USER STORY Work item
Dominant language
No language data
Stars
61
Forks
2
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
Not a problem, per se, just a frustration at the inefficiency.
We promote our work from our dev environments to UAT sandbox. During user testing, sometimes things fail, or the users come back to us with requested changes. Since we've promoted the Work Item, we are unable to do any more work associated with it. Instead, we have to create a new Work Item for the requested changes or fixes, basically redoing what we did when we set it up initially. If this happens more than a couple of times, we can end up with a bunch of work items that are not linked in any way, and unless we enforce a naming convention or something.

**Describe the solution you'd like**
Ideally, I would like to be able to continue to work in the same Work Item after it's been promoted, continuing to promote changes until it passes UAT and is ready for staging. If that's not possible then I would like a way to clone a work item so that I don't have to type in all the information again, set up the environments, etc, and also have any clones work items linked to the original some how so that no associated work is missed.

**Additional context**
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.