Closed luzpaz closed 10 years ago
Hmm, might make sense for only one bug.
But, what would happen or should happen, if you specified a comment for a list of bugs?
<mantis>
status = open
comment = blah, this is a comment
</mantis>
It's sort of an hacky response:
Just append the same comment to each issue.
or
you can specify
comment_#bugid = this comment is only for #bugid
and have logic in place to just search and see if there is a comment with the same bugid # as listed ?
I have to think about this for a bit.
Right now I rather tend to only allow the proposed comment field for a single bug (it would be ignored for a list or status query).
On the other side, I'm not quite sure, if such a field is really necessary. You can always add the comment before or after the bug:
This bug should be closed
<mantis>
bugid = 4
color = true
header = true
show = id, category, priority, created, updated, summary
</mantis>
Things like that should rather be done in the Mantis system by changing the summary. At least that's my opinion. But I'll think about it.
Hey @tessus, thanks for your response. Adding a comment before or after the bug breaks up the uniformity of the table on the wiki page. So it's an esthetic issue. Thanks for your attention and consideration. Very gracious of you to consider this. Cheers
I've implemented it, but I still have to write the documentation.
You can add comments by using the format:
comment<delimiter><bugid> = text.
, where <delimiter>
can be any character.
<mantis>
bugid = 4, 8, 13, 42
show = id, category, priority, created, updated, summary
comment.4 = This bug should be closed
comment/42 = Answer to the Ultimate Question of Life, The Universe, and Everything
comment#13 = Friday
</mantis>
Updated documentation at https://www.mediawiki.org/wiki/Extension:Mantis
This makes a real difference :+1: along with comma separated issue #s :+1: Thank you! Cheers!
You're welcome.
The 'comment' parameter would append another column after the last 'show' parameter