Yes I agree that Github offers more freedom on how one deals with an issue which can be a disadvantage if you want to force users to form a specific workflow on reporting issues.

On Tue, Apr 7, 2015 at 6:30 PM, Peter Uhnák <i.uhnak@gmail.com> wrote:
On Tue, Apr 7, 2015 at 5:11 PM, kilon alios <kilon.alios@gmail.com> wrote:
what kind of advantages does bitbucket offer over github on issue reporting ?

I am no contributor to Moose myself so I can't offer an informed opinion on this choice. But I love working on github and I think the whole pull request design is just brilliant with also the ability to comment and reply on commits and pull request and even attach issue reports to commits and pull requests. 
 
As far as pull requests go, on top of what GitHub provides, Bitbucket also allows you to specify reviewers and "approve" system.

But about issues - GitHub provides you some labeling system but it has NO structure whatsoever. 
Bitbucket on the other hand has many features like type (new, resolved, on hold, invalid, ...), priority, status, and even custom attributes, and more. Doing this with GitHub label is extremely heavy-handed. 

It also comes down to what kind of management you require. If you are ok with ad-hoc, then GitHub is perfect (since you don't need to deal with all the stuff mentioned above), but when you need proper organization, I cannot imagine doing it with just labels.

So, just sharing my 2¢.

Peter

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev