On 12/11/15 22:35, Andrea Aime wrote:
> Ben, whatever "transitions" us from talking less about procedures, leaving
> more time to actually fix
> bugs and improve the code, is a most welcomed step (less chat more splat,
> as Jody normally puts it) :-p
>
> I'd make a backup, just to be on the safe si
On 12/11/15 22:30, Andrea Aime wrote:
> I checked by I don't see the new workflow?
Jira "helpfully" hides workflows when looking under projects. You can
see the full list in Administration / Issues / Workflows / Inactive and
the osgeo one at the bottom.
> Anyways, I'd go for anything that's as
On Thu, Nov 12, 2015 at 10:31 AM, Ben Caradoc-Davies
wrote:
> If you use Jira, you have a workflow. I think Frank just wanted to be able
> to resolve an issue, which does not seem unreasonable to me. My small
> workflow tweak can enable a path to resolution for every issue, but is
> there a risk
If you use Jira, you have a workflow. I think Frank just wanted to be
able to resolve an issue, which does not seem unreasonable to me. My
small workflow tweak can enable a path to resolution for every issue,
but is there a risk of destroying Jira? Do we need a backup first? Or
just ignore it (
On Thu, Nov 12, 2015 at 1:06 AM, Ben Caradoc-Davies
wrote:
> Jody and Andrea,
>
> I have created an osgeo workflow and scheme but have not yet switched any
> projects to it. The new workflow removes "Patch Pending" and "With
> Customer". It differs from the old scheme by ensuring each of "Iterati
Hi Ben,
imho we should just forget about the workflow, to me it's just pointless
overhead.
No objections to have one if others feel the need to have one, but don't
think it might
have any meaning to those that perform gardening in jira in their spare time
Cheers
Andrea
On Thu, Nov 12, 2015 at 1:
I do not believe so, I was doing my best to go with Jira defaults.
The only thing I can think of is that some of the states were introduced
when restoring content via rest api?
--
Jody Garnett
On 11 November 2015 at 23:30, Ben Caradoc-Davies wrote:
> Jody and Andrea,
>
> Frank has an issue tha
Jody and Andrea,
I have created an osgeo workflow and scheme but have not yet switched
any projects to it. The new workflow removes "Patch Pending" and "With
Customer". It differs from the old scheme by ensuring each of
"Iteration", "Submitted", and "Analysis" have a transition back to "Open".
AFAICT uDig make extensive us of "Analysis", and we have one each in
GeoServer and GeoTools in "Submitted" for I suspect no good reason.
On 12/11/15 12:30, Ben Caradoc-Davies wrote:
> Jody and Andrea,
>
> Frank has an issue that is in the Jira "Submitted" state. This state has
> no outgoing trans
Jody and Andrea,
Frank has an issue that is in the Jira "Submitted" state. This state has
no outgoing transitions and so cannot be modified, even by an
administrator. Furthermore, because this state has no outgoing
transitions, the workflow cannot be modified to add an outgoing
transition (thi
10 matches
Mail list logo
