Closed luzpaz closed 10 years ago
Interesting proposal. I've never thought of that because I assumed people would just create a separate status entry (in Mantis) for bugs like that (eg. 2bClosed) and use it with the status keyword. But I see your point.
There are a few things I have to take into consideration though. When specifying a bug by id, header
and color
are off by default, which makes sense since it is just a single bug. But if I specified several bugs, the result would become a list and in that case header and color should be on by default (as with specifying a status).
I have already plans for tonight, so I won't be abe to implement it right away. I should be able to work on it on Monday.
I assumed people would just create a separate status entry (in Mantis) for bugs like that (eg. 2bClosed)
We at Scribus haven't customized special Statuses in our ManisBT, I think that would be a good idea. That could change our orientation. I will pass the word on.
Implemented in b28ce42.
bugids can now be specified as a comma separated list. Invalid values (e.g. strings) are ignored. If only a single bug is specified, header
and color
are turned off.
Thanks!! Will test and report
See http://wiki.scribus.net/canvas/Bugs_to_be_Buried#1._Bugs_to_be_closed for the reason why