Hi Mark,

I actually recommend we move to the simplified "JIRA workflow" I had 
proposed a while back [1].  We can obviously tweak it as needed though.

The only reason I haven't pushed to implement this simplified workflow 
yet is that I worried about causing problems with the 3.0 release 
process (as this JIRA workflow change will require a LOT of issue 
statuses to be updated, and I don't want to confuse folks as we work to 
get 3.0 out the door)

So, long story short, I suggest we revisit this after 3.0, and work to 
improved how we use JIRA in general.

[1] https://wiki.duraspace.org/display/DSPACE/JIRA+Workflow+Improvements

- Tim

On 10/26/2012 2:01 PM, Mark H. Wood wrote:
> There seems to be some disagreement about the meaning of "resolved".
> It *is* a bit ambiguous, given that another state is named "open" and
> a "resolved" item is not "open"...but neither is it "closed".
>
> I always thought that "resolved" meant something like "the assignee
> thinks this is fixed, would someone having this problem please
> confirm".  An issue would move to "closed" when it is confirmed fixed.
>
> There's one other transition to consider:  I think it should be normal
> to move an issue from "resolved" to "closed" if it has been "resolved"
> for a reasonable length of time and no one has remarked that the
> problem is not fixed.
>
>
>
> ------------------------------------------------------------------------------
> The Windows 8 Center
> In partnership with Sourceforge
> Your idea - your app - 30 days. Get started!
> http://windows8center.sourceforge.net/
> what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/
>
>
>
> _______________________________________________
> Dspace-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to