My 2 cents for using Scrum board for prioritize tickets and group these into Sprints to plan for a release.
And Its high time we remove outdated tickets as you proposed and for Ticket status, resolved to closed state should be done by reporter . It may be QA or developer from my prospective. Regarding the name changes, components need to be intact with project names <https://wiki.iotivity.org/projects_and_functions> . And I prefer existing name for discovery & connectivity than discovery & expiry as new name does not give much information about what it covers. Regards, Ashok From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Christian Gran Sent: Wednesday, March 22, 2017 3:34 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] Jira usage and Jira update Hi, as "Planning Function Lead? for IoTivity started to look a bit in how we use Jira :-) In my opinion we could do a few changes here and there and we would also benefit if we would update to the latest version. This would make the overall planning process for IoTivity a much easier :-) I have created two Wiki pages - one for proposed changes to Jira and one with proposals how we could use Jira. https://wiki.iotivity.org/jira_proposed_changes https://wiki.iotivity.org/jira_how_to_use My proposal is also to use the Scrum Board, which seems to be included in the latest version: https://www.atlassian.com/software/jira/agile#scrum With the Scrum board we could much better prioritize tickets and group these into Sprints to plan for a release. Any thoughts on this? thanks Christian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170322/846a7a52/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 201602111742151_N3WZA6X7.png Type: image/png Size: 33527 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170322/846a7a52/attachment.png>
