[cle-release-team] Jira management - Functional Testing user

[Aaron Zeckoski]

For that rare circumstance, I think a subtask should be created. In
fact, subtasks might be a better option for both of these.

I think we should aim for simpler solutions rather than complex ones.
-AZ


On Tue, Aug 28, 2012 at 4:24 PM, Neal Caidin
<nealcaidin at sakaifoundation.org> wrote:
> That sounds okay, but is it possible that an issue needs functional and technical testing? Maybe we should have two flags. One flag would be checked by default - Functional Testing, and one flag would be unchecked by default - Technical Testing.
>
> Thanks,
> Neal
>
> On Aug 28, 2012, at 9:27 AM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>
>> We used to (and sorta still do to a degree) use users as a filter and
>> it is not a practice that atlassian encourages (or to be more accurate
>> they actively discourage it). In the case of functional testing
>> (basically what everyone thinks of as QA), it is going to be needed in
>> the majority of cases so rather than adding work which has to be done
>> in most cases, why not only add a flag or something to indicate when
>> technical testing is needed?
>> Cases where no testing is needed are already handled by the developer
>> simply marking the item as verified/tested or closed.
>>
>> Generally only admins can others to a ticket as a watcher. Anyone can
>> add themselves. This is to prevent an average user from adding or
>> removing people from a ticket when they should not.
>>
>> -AZ
>>
>>
>> On Tue, Aug 28, 2012 at 9:12 AM, Neal Caidin
>> <nealcaidin at sakaifoundation.org> wrote:
>>> Hi All,
>>>
>>> I wanted to get some feedback on a minor, but helpful, change I would like to make to the process for managing Jira tickets. I have added the user account functest (which auto-correct tried to make "funkiest") with the name "Functional Tester".  I want to make it part of our process to assign functest to a ticket when we know that functional testing is needed. Then, for QA, we can easily filter which tickets specifically need QA testing.
>>>
>>> We could add functest as a Watcher or as the Assignee. The Assignee makes more sense to me from a workflow perspective, since we are assigning the task, but I guess the downside is that if the QA tester needs to reopen the issue, he will have to reassign to the original Assignee (which you can easily get from the ticket History). Whereas with Watcher, we don't have to worry about reassigning the ticket to the correct person, and we can still do the filtering we need (we just need to search on Resolved tickets that have Functional Tester as a Watcher). Does everybody have the ability to add Watchers, or only administrators (in which case Assignee would be better)?
>>>
>>> If this looks useful, I was also thinking of a adding a user account called "Technical Review" as a flag for code review or other types of technical review.
>>>
>>> Thanks,
>>> Neal Caidin
>>>
>>> Sakai CLE Community Coordinator
>>> nealcaidin at sakaifoundation.org
>>> Skype: nealkdin
>>> AIM: ncaidin at aol.com
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> cle-release-team mailing list
>>> cle-release-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>
>>
>>
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile