[Building Sakai] Jira Workflow

[Bryan Holladay]

Is there a reason this is locked down?  I would advocate opening it up
to everyone.  I can see an argument for locking it down like "we only
want peer reviewed users who we entrusted to make these decisions" but
I think that makes us lose out on the people who are volunteering to
help out who usually don't.  Even if they do help out still, then we
lose the whole point of the workflow since they can't change it.  Is
this a rampant issue in Jira?

-Bryan

On Wed, Apr 4, 2012 at 9:00 AM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
> There are permissions in the workflow so if you are not able to see
> parts it is because you are missing things like the developer or QA
> permissions. This can be easily controlled by each project as they
> simply need to add a person to the role in their project for developer
> or QA or administrator to give them access to those parts of the
> workflow.
>
> We can also control it at the system level for people (for example,
> anyone who is an active member of the QA team has global permissions
> to use those parts of the workflow).
>
> -AZ
>
>
> On Wed, Apr 4, 2012 at 8:34 AM, Bryan Holladay <holladay at longsight.com> wrote:
>> Is everyone seeing the workflow options?  I did QA'ing on Samigo
>> yesterday and we found out that some people had the workflow dropdown
>> options and others (like me) had that button greyed out or only had 1
>> option "Unreviewed".  There was also another button that said "Close
>> without testing".  Is this a permissions issue in jira?  Anyone else
>> seeing this?
>>
>> Thanks,
>> Bryan
>>
>> On Wed, Apr 4, 2012 at 6:48 AM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>>> I resolved and reopened it to force the resolution status field to
>>> "unresolved". I think subtasks just inherit fields from the parent
>>> when they are created.
>>>
>>> -AZ
>>>
>>>
>>> On Wed, Apr 4, 2012 at 6:08 AM, Jean-Francois Leveque
>>> <jean-francois.leveque at upmc.fr> wrote:
>>>> I've opened and converted a sub-task into a feature request issue, but
>>>> it still has Resolution set to Won't Fix.
>>>>
>>>> What should I do to get rid of the resolution now?
>>>>
>>>> If you wanna check, the issue is
>>>> https://jira.sakaiproject.org/browse/SAK-19648
>>>>
>>>> Cheers,
>>>>
>>>> J-F
>>>> _______________________________________________
>>>> sakai-dev mailing list
>>>> sakai-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>
>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>
>>>
>>>
>>> --
>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile