Developing Bugs

[friarsol]

I generally Resolve bugs I add code for, and Close bugs I don't add code for (can't reproduce, or something that's already been fixed). In theory, a QA team would go through and verify the bugs that are resolved. If they are still around, then the bug can be reopened. Otherwise, the QA team would close them out.

[Max mtg]

Did mantis send an email to you when I resolved some issues you reported?
Maybe it is not just set up and reportets don't know about their issues' updates?

[friarsol]

I get lots of emails from Mantis because I'm an admin on there, so I don't know whether or not other people get them.

[ArsenalNut]

I get lots of email from Mantis but I don't think I get email for everything. I don't usually read the emails. I mostly use the emails as a reminder to check Mantis for anything related to changes I've made.

On the topic of Mantis, do we have guidelines for assigning issues to developers. In general, I can figure out why an issue occurs but it may be in part of the code I am not familiar with. In these cases, it will get fixed faster if it is assigned to someone more familiar ,e.g. the person who made the most recent change, than me.

[friarsol]

On the topic of Mantis, do we have guidelines for assigning issues to developers. In general, I can figure out why an issue occurs but it may be in part of the code I am not familiar with. In these cases, it will get fixed faster if it is assigned to someone more familiar ,e.g. the person who made the most recent change, than me.

We don't really have a "War room" where bugs get assigned. And since all the time is volunteered, assigning a bug to someone won't necessarily mean it'll get fixed faster. But it might be good to have a way where you can suggest bugs to people if you know that's an area they've worked in. (eg. "suggesting" I check out a Cost bug, since I just revamped it)

Although, I don't know how that system would work in reality.

[slapshot5]

How do I close a bug in Mantis?

[ArsenalNut]

How do I close a bug in Mantis?

There should be a row of buttons right under the "Attached Files" field. One of the buttons is "Change Status" with a pull down for choices.

If you don't see this button then you probably aren't setup as a developer role in the Mantis tool. Check next to your name and see what role you are currently assigned. I believe only developers and administrators can change the status of a reported issue.

[slapshot5]

How do I close a bug in Mantis?

There should be a row of buttons right under the "Attached Files" field. One of the buttons is "Change Status" with a pull down for choices.

If you don't see this button then you probably aren't setup as a developer role in the Mantis tool. Check next to your name and see what role you are currently assigned. I believe only developers and administrators can change the status of a reported issue.

I have Monitor, Reopen, Move, Delete

Looking at: http://cardforge.org/bugz/view.php?id=273

It says developer next to my name.

-slapshot5

[ArsenalNut]

How do I close a bug in Mantis?

There should be a row of buttons right under the "Attached Files" field. One of the buttons is "Change Status" with a pull down for choices.

If you don't see this button then you probably aren't setup as a developer role in the Mantis tool. Check next to your name and see what role you are currently assigned. I believe only developers and administrators can change the status of a reported issue.

I have Monitor, Reopen, Move, Delete

Looking at: http://cardforge.org/bugz/view.php?id=273

It says developer next to my name.

-slapshot5

I think only someone that is an administrator can move it to the closed state.

[slapshot5]

I think only someone that is an administrator can move it to the closed state.

Can we change that? Bugs will never get closed this way. It would be ideal if any Admin, Devel, or the original reporter can close the bug.

-slapshot5

[Max mtg]

i recently managfed to close some - it was a mass operation performed on a list of cards

Pls, add 1.1.4 version to mantis

[friarsol]

I think only someone that is an administrator can move it to the closed state.

Can we change that? Bugs will never get closed this way. It would be ideal if any Admin, Devel, or the original reporter can close the bug.

-slapshot5

Slap,
You don't see the Change Status button with a dropdown next to it? See attached

[ArsenalNut]

I think only someone that is an administrator can move it to the closed state.

Can we change that? Bugs will never get closed this way. It would be ideal if any Admin, Devel, or the original reporter can close the bug.

-slapshot5

Slap,
You don't see the Change Status button with a dropdown next to it? See attached

I think SlapShot is talking about moving something from the resolved state to the closed state. I can close something if it's not in the resolved state but once it's in the resolved state, all I can do is reopen it.

[friarsol]

I think SlapShot is talking about moving something from the resolved state to the closed state. I can close something if it's not in the resolved state but once it's in the resolved state, all I can do is reopen it.

That's stupid. I think I just changed the option in the prefs that wasn't allowing Devs to close bugs. See if that has fixed it?

[ArsenalNut]

I think SlapShot is talking about moving something from the resolved state to the closed state. I can close something if it's not in the resolved state but once it's in the resolved state, all I can do is reopen it.

That's stupid. I think I just changed the option in the prefs that wasn't allowing Devs to close bugs. See if that has fixed it?

That fixed it. I just closed 225 as a test.