Forum OpenACS Development: Re: OpenACS: the core and the packages/plugins

Collapse
30: Re: OpenACS: the core and the packages/plugins (response to 29)
Posted by Gustaf Neumann on 01/14/21 09:23 PM
The "bug-tracker" instannce on openacs.org is a package from the HEAD branch and it works with acs-core from oacs-5-10; Most of the package at openacs.org are from the oacs-5-10 branch.
Collapse
31: Re: OpenACS: the core and the packages/plugins (response to 30)
Posted by Maurizio Martignano on 01/14/21 11:08 PM
Dear Gustaf,
thank you for having answered me. I asked the above question because I think I noticed a strange behaviour in the bug-tracker in my Windows distribution. I have to say I'm relieved to see that the very same behaviours occurs also in your standard installation. Perhaps I'm misusing the system. I'll try to explain here:

1. I entered a test bug as shown in here:
https://spazioit.com/images/naviserver/bug_error01.jpg

2. I edited the difficulty and priority of this bug and when you do so
the corresponding fields disappear when you click on the bug,
as shown in here:
https://spazioit.com/images/naviserver/bug_error02.jpg

3. I tried in any way to modify the difficulty and priority of this bug,
as shown in here:
https://spazioit.com/images/naviserver/bug_error03.jpg
but whatever I do the main list always shows me what we had
before:
https://spazioit.com/images/naviserver/bug_error01.jpg.

Am I doing anything wrong?

Thank you in advance,
Maurizio

Collapse
36: Re: OpenACS: the core and the packages/plugins (response to 34)
Posted by Maurizio Martignano on 01/15/21 11:11 AM
Dear Gustaf,
It really seams related, thank you!

(I'm less worried now. Seeing that the issue is a general one and not a "Windows" one, has relaxed me quite a bit.)

Again thank you,
Maurizio

Collapse
37: Re: OpenACS: the core and the packages/plugins (response to 34)
Posted by Gustaf Neumann on 01/15/21 12:52 PM
Concerning bug tracker workflows: The intended workflow is as follows:

Some user A opens an issue, many people can comment, the maintainer M should resolve the issue, then A should either close or reopen it. It can also be reopened later.

Design: https://openacs.org/doc/bug-tracker/bug-tracker-spec