I'm looking for a part-time remote job.

Hire me


I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).


Follow me:

Feature #2383

Multiselect for Project fields

Added by Joshua Rosen over 4 years ago. Updated about 4 years ago.

Status:
Open
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

External issue:

Description

I’d really like to be able to add a custom field of type Project to issues so that I can indicate multiple other projects that should be tested before closing an issue that involved code-changes; e.g.:

  • if two projects share any code, when implementing a feature for one of them there’s the possibility of accidentally affecting the other, and the other flagged projects should be tested before closing the issue
  • a project that is part of a larger system may have severe bugs that are known to affect other parts of the system, in which case those other flagged projects should be tested before closing the issue

It’s awkward (at best) to implement such a field where only one auxiliary project can be selected.

History

#1 Updated by Andriy Lesyuk about 4 years ago

  • Status changed from New to Open
  • Assignee set to Andriy Lesyuk

Also available in: Atom PDF

Terms of use | Privacy policy