[Building Sakai] [DG: User Experience] Feature requests for Sakai OAE

[John Norman]

Perhaps the right way to think about this is to use JIRA for issue tracking and try this new thing for developing ideas and turning them into trackable issues.

Just a thought from someone who's heart sinks every time he has to use JIRA. It really is a developer tool.

J

On 27 Aug 2011, at 23:03, Steve Swinsburg wrote:

> Jira has worked well for the Sakai CLE over the years, there is a feature request issue type, priority and voting. You can create filters to find all sorts of issues. 
> 
> I'll suggest sticking with Jira. Moving to something else risks fragmenting the two projects further. 
> 
> Steve
> 
> Sent from my iPhone
> 
> On 28/08/2011, at 3:17, "N. Matthijs" <nicolaas.matthijs at caret.cam.ac.uk> wrote:
> 
>> Hi everyone,
>> 
>> Now that Sakai OAE is entering a phase with a lot more deployments
>> and users using OAE, we've seen an increase of feature requests
>> and suggestions for improvements in JIRA.
>> 
>> In this instance, I'm referring to a feature request as a user-facing
>> change or improvement, which most likely needs some design
>> attention as well. An example of such a feature request would be
>> SAKIII-3609 [1].
>> 
>> However, bringing them in via JIRA is probably not the best
>> way to go about this. They're mixed in between a ton of other
>> JIRA tickets, so it's very easy for them to get lost. I've been
>> keeping a list of requests in a document, but it's not the best
>> way to do this and a lot of them don't make it to design. Putting
>> them in JIRA also makes it hard to prioritize them and get people
>> to weigh in as to why they are important. However, up until now
>> there hasn't been a better way to raise these, and I really don't
>> want these to get lost.
>> 
>> Therefore, I'd like to suggest that we try and use [2] for submitting
>> ideas for improvements and new features. This allows people to
>> submit ideas and vote on existing ideas. This should make it easier
>> for design to get a better idea of what the most critical issues are.
>> It's not the best or the prettiest system, but it is free and it is very
>> easy to get the data back out if we have to, so I think it's worth a
>> try.
>> 
>> I've also added a link to this into the OAE footer (will be in the v1.0.1
>> release). This will allow end users to make suggestions and vote as well,
>> and being able to collect this from across the community should be very
>> powerful.
>> 
>> I've already put some of the requests for new features that were
>> currently in JIRA into this system.
>> 
>> Suggestions for technical improvements or areas to make configurable
>> are definitely still fine to go into JIRA. An example of such a ticket would
>> be SAKIII-1973 [2]
>> 
>> [1] https://jira.sakaiproject.org/browse/SAKIII-3609
>> [2] http://sakaioae.idea.informer.com/
>> [3] https://jira.sakaiproject.org/browse/SAKIII-1973
>> 
>> Kind regards,
>> Nicolaas
>> 
>> _______________________________________________
>> 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"
> 
> _______________________________________________
> sakai-ux mailing list
> sakai-ux at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-ux
> 
> TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

John Norman
Director - CARET
University of Cambridge
john at caret.cam.ac.uk
+44-1223-765367

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110828/bceaedd9/attachment.html