andymac-2 / milestoneMap

Milestone tracking application
Other
1 stars 4 forks source link

Add in a time stamp on report name #15

Closed PritchardBarry closed 6 years ago

PritchardBarry commented 6 years ago

screen shot 2018-04-26 at 9 04 51 pm

andymac-2 commented 6 years ago

The name of the report, and the report date can be changed by clicking on their respective names and dates just above the date bar, allowing you to differentiate between them. Perhaps this is the feature you're looking for?

PritchardBarry commented 6 years ago

Not quite.

If I just rely on the program to choose the name I get the report names as shown in the screenshot. I have 2 separate reports with the same name "New Report: 2018-04-26" I can't distinguish between them.

What I want is to easily be able to see the sequence the reports are created in (just having the names in order is not intuitive enough).

What I also want to enforce is that a snapshot can only be compared to an earlier snapshot. I thin this means that, depending on the report selected in the "Current" option that only reports created earlier should show in the "Baseline" option.

PritchardBarry commented 6 years ago

It is still great to be able to give a report a user friendly title though.

andymac-2 commented 6 years ago

If I just rely on the program to choose the name I get the report names as shown in the screenshot. I have 2 separate reports with the same name "New Report: 2018-04-26"

I'm not sure I understand. If that's the case, simply rename one of the reports to differentiate between them. The program is not meant to create unique names for you. e.g. call one report "Optimistic Forecast" and another one "Pessimistic Forecast" to differentiate between the two.

What I also want to enforce is that a snapshot can only be compared to an earlier snapshot.

You can change the date of a report to whatever date you like, and that will break your ability to compare only reports from the past. If a user wanted to create a new report, and then change the date from a default date after to a new date before the report that was currently loaded as the comparison, (or vice versa) then this would require four actions to complete: (change date to comparison date, switch baseline and comparison reports, change date to desired date) rather than one (change date to desired date).

The date of the report is not meant to be today's date either, it represents a reporting date, whether that be in the future or the past. (eg, you could compare a pessimistic estimate to an optimistic one for the same day, or the other way around). I imagine that no meaningful changes of milestone dates happen within a single day, enough to warrant creating a new report?

PritchardBarry commented 6 years ago

Usability requirement

simply rename one of the reports to differentiate between them. The program is not meant to create unique names for you

This relies on the user doing the right thing and keep track themselves. Unfortunately the user is the weakest link. Even if it is a simple numeric sequence number we need to provide a means to differentiate between older and newer reports. The assumption when comparing is that the "white" milestones are in the past.

You can change the date of a report to whatever date you like, and that will break your ability to compare only reports from the past.

Agreed, which is why I would like to enforce an internal sequence number and prevent the user from selecting incorrect matches. Think of the sequence number as the unique report ID and the name and date you allow to be edited as separate attributes.

andymac-2 commented 6 years ago

Is this still required?

andymac-2 commented 6 years ago

Closed as no longer required