Hi,

I created one report with a new tag '0.9.30', so I can easily find bug report related to the fixes_0_9_30 branch.

I did a "view issues" and selected '0.9.30' tag as filter. It only showed one bug report. I went back to my previous bug reports and the '0.9.30' tag was removed for all but the last bug report.

So it seems Mantis only allows one bug report to have one tag. That is stupid! What's the point of tags then, if you can't reused them?

Usage:
In each case, I selected the '0.9.30' tag from the dropdown list, and selected "Attach". The tag then appeared in the 'Tags' column. But that also removed the tag from all other bug reports. :-(

Regards,
- Graeme -

OK, I just got a Mantis report email which listed that Vincent removed all the tags - believing they are unnecessary.

Personally, I don't think so, because now all 0.9.30 related reports fall under the 0.9.29 version - which was also the Trunk a little while ago. So now there is no way to distinguish between older 0.9.29 (Trunk) reports and newer reports relating to 0.9.30 branch.

Regards,
- Graeme -

2011/1/5 Graeme Geldenhuys :

Why do you need to distinguish?

If it was an issue in the 0.9.29 version while it is was in trunk or in the 0.9.29 while it was in the fixes_0_9_30 branch, both issues end up in 0.9.30, if they are not fixed.

Vincent

2011/1/5 Graeme Geldenhuys :

You could have checked the history to see, that I removed that tag.

I thought you only added it because there was no version 0.9.30 to choose from. I explained earlier why that is, so there was no need to add that tag.

Vincent

Op 2011-01-05 11:11, Vincent Snijders het geskryf:

I thought you only added it because there was no version 0.9.30 to choose from. I explained earlier why that is, so there was no need to add that tag.

By the time I read your reply and explanation, I already reported about another 4 bugs with attached tags. My new bug reports don't have attached tags.

I just thought being able to distinquish between old Trunk and new fixes branch, whould be easier for developers wanting to "stablize" the fixes branch, or easy to use Mantis to see what fixes in current Trunk needs to be back-ported to fixes branch (because the original bug report was filed against the 0.9.30 branch). But if you guys have a workflow that already does all this, then sorry for the noise.

Regards,
- Graeme -