Community driven Bug&Issue Tracker (CIT) for ARMA 2: Operation Arrowhead and ARMA 2

[DBGB]

I was wondering about the way that users at dev-heaven in the community issue tracker can vote a bug/feature/etc. up in the same way that a Product Owner (as viewed within a Scrum development framework) decides priorities for a product backlog item?


So th BI devs use the CIT tickets to monitor potential product backlog items and pick 'public CIT' items for the next sprints ?

Just curious about the similarities - Don't know if this is the right forum for this post.....feel free to move this post to the sprint backlog ;-)

[.kju [PvPscene]]

BI checks high voted tickets more likely yes. Yet it is not the only aspect for that.
Very important is ticket quality (short, precise, required info present), as well as type
(CTD/AI/engine and a few others have high(er) chance, model/world and a few others
are unlikely to get look into at this point).
Finally there is also personal interest of the coder and usefulness for future products.

I cannot answer your main question, but from what I can tell they dont use strict
SCRUM product backlog principles.

[[GLT] Legislator]

I'd like to ask a question. Will someone of the devs browse through the CIT to close tickets which won't be taken care of anyway? This way it would be far more easier to browse the latest issues.

[OMAC]

In dev-heaven, how does one add a project to one's Favorite Projects list?

[.kju [PvPscene]]

You need to get member status for it. Ask a manager of the project to make you tester or another role.

[OMAC]

You need to get member status for it. As a manager of the project to make you tester or another role.

Got it. Thanks.