Not signed in (Sign In)
The Intervals Forum is Closed.
This forum has been replaced with a help section located at help.myintervals.com.
We recommend checking the help section, as the forums are no longer being updated. If you have any questions, please don't hesitate to contact our support team.

Feature Requests

Nested Milestone or Sub Tasks

Bottom of Page

1 to 3 of 3

  1.  
  1.  

    Hello!

    We are migrating our business to your system and can say we are really liking what we are seeing so far!

    The new milestone feature was the feature that got us onboard with Intervals 100%.

    We would love to have the following added in a future update to Milestones and Tasks. Two parts of our company develop software and software products that contain features and work to implement the features. We have to number them so they will sort in a fashion we can differentiate the work being done by feature in the main software project. Currently in Intervals we have to set this up like so:

    [Main Software Project]:

    # Milestone 1: Development Phase (total 130 hours projected)
    -- Feature 1.0 (main task of feature 1, 0 hours)
    -- Feature 1.1 (sub task of feature 1, 30 hours)
    -- Feature 1.2 (sub task of feature 1, 30 hours)
    -- Feature 1.3 (sub task of feature 1, 30 hours)
    -- Feature 2.0 (main task of feature 2, 0 hours)
    -- Feature 1.1 (sub task of feature 1, 20 hours)
    -- Feature 1.2 (sub task of feature 1, 20 hours)

    # Milestone 2: QA Phase
    -- QA Work Effort 1.0
    -- QA Work Effort 1.1
    -- QA Work Effort 1.2
    -- QA Work Effort 1.3
    -- QA Work Effort 2.0
    -- QA Work Effort 2.1
    -- QA Work Effort 2.2
    -- QA Work Effort 2.3

    (etc...)

    As you can see, the features have subtasks that must be done before the main feature can be ready so the whole milestone can be complete to pass to the next phase (Dev-> QA-> Public Beta-> then Release to Market (where the project is then closed)). Also, there is no way for us to quickly find out the time tracked for each feature under the milestone.

    What we would love is to have nested milestones or subtasks so we can breakdown the Features to track work behind done on them. This would allow us to use Interval's very nice time tracking to budget time for each feature in our software and track and report, feature by feature, its progress. The idea is that we could 'roll up', track and budget the hours for each feature under the milestone.

    We only really need one level of nesting to help organize the sub work under each milestone.

    [Main Software Project]:

    # Milestone: Software Development Phase (total 130 hours projected)
    -- Feature 1 (main task of feature 1, 90 hours budgeted)
    ---- Subtask 1 (sub task of feature 1, 30 hours)
    ---- Subtask 2 (sub task of feature 1, 30 hours)
    ---- Subtask 3 (sub task of feature 1, 30 hours)
    -- Feature 2 (main task of feature 2, 40 hours budgeted)
    ---- Subtask 1 (sub task of feature 2, 20 hours)
    ---- Subtask 2 (sub task of feature 2, 20 hours)

    # Milestone: Software QA Phase ...
    -- QA Work Effort 1 ...
    ---- Subtask 1 ...
    ---- Subtask 2 ...
    ---- Subtask 3 ...
    -- QA Work Effort 2 ...
    ---- Subtask 1 ...
    ---- Subtask 2 ...
    ---- Subtask 3 ...

    We really enjoy Intervals, but going forward this feature would be very very helpful to us in keeping things organized, but also in tracking/reporting on features within a milestone nicely.

    ~George

  2.  

    I would really really like to be able to add Subtasks (aka To-Dos) in a fast "checklist" format, without a screen refresh.

    To compare with Basecamp/Backpack once again: they allow the quick addition of to-dos that can then be ticked 'done', checklist-style. This would be SO helpful, I would cry if you implemented it. Example of content:

    Make Sandwich (Task)
    - jam
    - PB
    - bread
    - knife

    Many tasks have components like this that need very fast addition. Tracking them as, say, bullet points in the Task description is only helpful to a point, because you can't mark them 'done', and it requires a screen reload to update the task details.

  3.  
    Would be wonderful!

Comments are closed.
For more Intervals help documentation, please visit help.myintervals.com