Redmine

h1. UXTeamMeeting1

Purpose: Review subtasking: #443

Meeting held via: Skype

Date / Time: "Tue May 11, 2010 21:00 UTC":http://www.timeanddate.com/worldclock/fixedtime.html?month=5&day=11&year=2010&hour=21&min=0&sec=0&p1=0

*To join the meeting*: add your name and skype ID below so Shane can invite you.

|_. Skype nick |_. Real Name |

| Shane Pearlman | Shane Pearlman |

| zanuda13 | Igor Balk |

| SikhNerd | Muntek Singh |

| angelkbrown | angel brown |

Meeting went off well. Notes taken by Shane Pearlman

h2. Action Items:

* Review the list of challenges and provide suggestions. Please put feedback here: http://www.redmine.org/boards/1/topics/13856

h2. Minutes:

*Meeting Goal*

* review http://www.redmine.org/issues/443

*Resources*

* Demo site: http://ux.redmight.com

Every night at 1am this pulls from trunk

All content is randomly generated

* JPL's news: http://www.redmine.org/news/36

* Continuous integration server running @ ci.finn.de

*Core Challenges Observed with Subtask Feature:*

# subtask and relationship are being handled speperatly when they are really the same thing

# parent task is not an available filter in the issue list

# should be able to assign any relationship from new issue form (including subtask) but cannot

# all relationships should be displayed in relationship box. Currently it only seems to show child issues in the subtask box while parent issues are displayed in the breadcrumb trail at the top of the issue. Suggestion to ditch breadcrumb trail and just show in relationship box.

# breadcrumb trail is ugly and unclear. It should follow standard breadcrumb look / feel. Concern: highly nested tasks? Is it unlimited or is there a max: x levels? (If suggestion from #5 is vetoed) Breadcrumb trail should do the same visual treatment as subprojects.

# there appears to be no way to make an existing issue a subtask of another issue

# cannot change (move?) subtask from one parent issue to another. Should also be able to un-subtask an issue (make top level)

# inheritance of time needs to be clear, either way we choose

# inheritance of status needs to be clear, either way we choose

Question: how much permission granularity should subtasks have - right now its just boolean - manage or not. We are ok with this, just wanted to note that it is a deviation from other permission patterns.

*Suggested Topic for next meeting*

Merge Files and Documents Features into one

initial recommendation  - display files uploaded to issues in an organized manner in main files (media library)

initial recommendation - allow files uploaded to be tied to versions (handles requirement from other feature)