Ability to defer issues
Description
I would love the ability to defer issues, because they are either blocked or you have to wait until some release before this issue becomes relevant. Deferred issues shouldn't pop up in the index view unless the user sets it as parameter in the search bar.
Inspired by: https://gitlab.com/gitlab-org/gitlab-ce/issues/30876#note_27381983
Proposal
We have a due date for issues, now I want something like it: a deferred date.
Links / references
Inspired by Omnifocus' deferred items.
Activity
added feature proposal label
Thanks @zj. Why invent a new native mechanism to hide issues? We have labels and other attributes. Admittedly we can't search on negatives just yet, but that's here:
https://gitlab.com/gitlab-org/gitlab-ce/issues/27747
As for dependency between relations, that starts here: https://gitlab.com/gitlab-org/gitlab-ee/issues/2001
@victorwu Because labels don't hide anything. Also, adding and removing labels is manual labour, which is a hassle. Furthermore, when you add and remove labels, these the systemnotes are quite verbose, even when its only for hiding a label. Last, labels are not at all pretty in the issues index page, nor the issue#show action once you have more than 2 or 3.
Thanks @zj :
Because labels don't hide anything.
#27747 (moved) solves that problem so that you can view a list of issues per the criteria you want, including hiding.
Also, adding and removing labels is manual labour, which is a hassle.
Any "deferring" feature would require some type of manual mechanism to mark it as such right also right? Or are you considering something else?
Furthermore, when you add and remove labels, these the systemnotes are quite verbose, even when its only for hiding a label.
I think that's a separate issue right? For any type of feature, we consider how we want to notify people, display an audit trail for people, provide a mechanism for people to collaborate on that action. So this is the same. Some features we have a system note. Some we have an email notification. We don't have everything for every action. So we would consider that as a separate concern I would think. As for verboseness of system notes, I do agree that's a concern, which we are alleviating in: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10667.
Last, labels are not at all pretty in the issues index page, nor the issue#show action once you have more than 2 or 3.
Sorry don't understand this one. What do you mean be "pretty"? What's the problem? Not understanding the issue#show action you are referring to either.
