Hi,
I have now created a workflow for SLING as follows:
* 3 new states
Documentation Required
can transition to Resolved
Testcases Required
can transition to Resolved
Documentation/Testcases Required
can transition to Documentation Required
can transition to Testcase Required
can transition to Resolved
* Issues in progress can transition to
- Resolved
- Documentation Required
- Testcase Required
- Documentation/Testcase Required
* Closed issues cannot be reopened
The idea is, that closed issues are part of a
released product and thus issues occurring in the
released product should raise new issues (may link
to old ones, though).
As a consequence of the last point, issues should generally be resolved
only. The release manager will then care to close the issues after release.
I will create a documentation page on this.
Regards
Felix
Bertrand Delacretaz schrieb:
> Hi,
>
> I have reopened https://issues.apache.org/jira/browse/SLING-922 to
> remind us to document this feature.
>
> We could also create another issue ("document SLING-922") for that -
> or does JIRA allow for "needs documentation" (and maybe "needs
> automated tests") states for such issues, where the coding is done but
> docs and/or tests are still missing.
>
> Does anyone know? If not I'll try to find out how JIRA could help manage this.
>
> -Bertrand
>
