Issues without target version still shown as late

[jamnanlaw]

For issues without a target version, I would expect that there is no late/due date.

However, in 0.4.0, a "shared with all" version will be used against those issues, like this:

[stgeneral]

For issues without a target version, I would expect that there is no late/due date.

Why not? Project's due date utilizes build-in method Project#due_date method:

class Project < ActiveRecord::Base
# ...
  # The latest due date of an issue or version
  def due_date
    @due_date ||= [
     issues.maximum('due_date'),
     shared_versions.maximum('effective_date'),
     Issue.fixed_version(shared_versions).maximum('due_date')
    ].compact.max
  end
# ...

So, plugin is just shows information without any changes to the default Redmine's logic. If you don't expect any due date I think you should not have any issue with a due date.

However, in 0.4.0, a "shared with all" version will be used against those issues, like this:

Same thing... It utilizes just build-in Version#effective_date method.

Let me know if I miss something.

[jamnanlaw]

Those issues are considered "product backlogs" in scrum term and are not scheduled yet.

They do not have any due dates set nor are they assigned to any specified shared versions. I don't see why a shared version or any version should be applied to them.

And I apologize for a very bad example in the screenshot above. It is actually showing a different but related bug - those 7 issues are all assigned to a target version - v201306, which has no due date . However, as you can see, it shows "6 days late" on the first section, while it is empty for the second section, which contains the same 7 issues. This does not make sense to me at all.

Please consider. Thanks.