Cross-Tagging bugs & assignments across 2+ projects

  • TrivialSeverity_star_large_inactiveSeverity_star_large_inactiveSeverity_star_large_inactiveSeverity_star_large_inactive
  • Marked as
    Discarded
  • Assigned to
    Nobody
#187 Reported over 5 years ago by Lech Deregowski (Participant)

If a user is managing two or more projects which just happen to share the same kind of base code for example. Giving the people involved in the project the ability to flag bugs within that project and other projects which may be affected by said bugs. Instead of having to navigate to each and every project then file a duplicate report this kind of report can just be written up once and applied to or removed from projects within a “super-group” of projects.

  • The Example: Say we have Project A, Project B, Project C, and Project D.
  • Projects A, B & D are all branched off the same code-base and C only shares minor trivial bits.
  • A user then creating a ticket can then easily just assign a ticket to multiple projects. This is if the owner has grouped said projects all without having that user file multiple tickets.
  • Else the owner can then re-assign one ticket to multiple project if necessary.
  • It would also save the developer / assignee some time of flipping through tickets.
  • Merging of tickets too maybe?

This would probably be a feature more useful for those accounts which can start more than 1 project, anyway. But a handy feature either way.


Discussion and changes

Post a comment
Over 5 years ago
Dan Glegg (Project owner)

I’ve been thinking about this feature and I’ve reached the conclusion that the size of the development would outweigh any benefit to the type of developer Tails is designed for.

Merging of tickets is however promising as it is a single-project action. I’ve created a new ticket for this feature alone.

Over 5 years ago
Dan Glegg changed status to Discarded
Over 5 years ago
Lech Deregowski created this

Terms of Service Privacy policy Report a problem with the bugtracker