Hello, Thanks for the heads up Anarcat – these are interesting changes indeed, and I agree that GitLab could have done a better job of easing them in. I think the main takeaway for most issue-filers (who aren’t involved in issue management or triage) is that the New issues button has changed to New item, regardless of the reversion. Is that correct?
To help migrate users to the new system, it may have been better if GitLab had retained the “Closed” tab as a default view for existing projects. I assume since views are now user-configurable, it could be easily removed or replaced if desired. However the “Closed” tab was never that useful for me, so I personally will not mourn its demise. (Others may disagree, of course). Despite that, the ability to save sets of filters as new tabs is appealing, and I really look forward to using this feature in my work. For instance, I can now create tabs that are based on statuses, labels, releases or assignees, instead of just “Open”, “Closed” or “All issues". Users also appear to be able to control whether new tabs are visible to themselves only, or to all members of the project. For power-suers, this is great! I’m sure Team Leads and PMs could get very creative with this feature. Unfortunately, however, I’m not able to create a new view at present – as I’m receiving the error “Saved views are not enabled for this namespace”. Perhaps I can look forward to this in future, when the wrinkles have been ironed out. —Duncan |
Attachment:
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ tor-project mailing list -- tor-project@xxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to tor-project-leave@xxxxxxxxxxxxxxxxxxxx