- Issue created by @ressa
- πΊπΈUnited States drumm NY, US
Issues are moving to GitLab, β¨ Move issues from www.drupal.org to git.drupalcode.org Postponed , so we are not building new features around issues.
- π©π°Denmark ressa Copenhagen
Is it possible to tweak GitLab, and add new features, such as the one suggested in this issue?
- π©π°Denmark ressa Copenhagen
Thinking some more about this, it would be sad if innovation and new Drupal issue features stopped, after a move to GitLab ...
Because, as a user, I could see this feature as useful, and not really care if it's a Drupal.org or GitLab customization in the backend.
- πΊπΈUnited States drumm NY, US
GitLab does not offer customization like Drupal has. This could be an upstream feature at https://gitlab.com/gitlab-org/gitlab/-/issues, but it's very specific and not something Iβve seen in other issue trackers.
GitLab does have additional project management tools, like epics and milestones, which might help prioritization and focus, although those will remain hard problems regardless of tools & technology we throw at it.
- π©π°Denmark ressa Copenhagen
Thanks for clarifying @drumm, that going forward, GitLab is probably the place to pursue this.
As on drupal.org, GitLab has a
priority::high
("Major") option. But my vision with this suggested feature, is that it should work on a personal priority level: An issue can have Priority Normal, if it's not an urgent problem, but many users may see great value in getting it completed -- such as a great.gitignore
out of the box, to onboard beginners. ( β¨ Add gitignore(s) to Composer-ready project templates Needs work )Maybe it could be something like a
personal-priority::high
flag on GitLab? :)