Re: Bug Tracker: organisation?

Willow Liquorice <[email protected]>
Newsgroups gmane.network.gnunet.devel
Message-ID <[email protected]>
Hello again,

A new role may be necessary. Seems relatively straightforward to 
implement, though, just by leafing through the manual, and you can 
figure out just what exactly an "updater" can do:

Creating roles: 
https://www.mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.user.access

Configuring roles (I think): 
https://www.mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.lifecycle.workflow.thresholds

I've noticed that I can only remove tags that I've added, and can't 
manage tags themselves.

I was thinking that one of the first things we could do is create a 
"Meta" project on the Bug Tracker, for identifying and discussing issues 
with overarching workflow (like the Bug Tracker, and maybe our build 
system). That way, these threads of conversation don't get lost in the 
mailing list. What do you think?

	- Willow

On 31/07/2022 18:21, Martin Schanzenbach wrote:
> I gave you the "updater" role now. See what you can do now.
> Not sure what kind of rights you need, but the problem is that mantisbt
> default roles are not really flexible (and I am hesitant to make you the
> project manager ;)
> I guess for issue maintenance, we may need another role(?)
> 
> BR
> 
> Excerpts from Willow Liquorice's message of 2022-07-31 17:55:17 +0100:
>> Hello,
>>
>> I'm a bit curious about how the bug tracker is organised, and who can do
>> what, because, outside of the roadmap, I'm not sure about how
>> well-organised the issues are. The tags certainly look quite cluttered,
>> and there seem to be a few users that seem to open unrelated issues
>> which stink of fraud.
>>
>> How many people can manage issues on the bug tracker? I'm willing to
>> take up some of the slack in keeping it organised, if that's OK with
>> everyone.
>>
>>      - Willow
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.