Opened 10 years ago
Last modified 10 years ago
#11663 closed enhancement
Milestone edit page should more clearly show when milestone doesn't exist — at Initial Version
Reported by: | Ryan J Ollos | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 1.0.2 |
Component: | roadmap | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When navigating from the Add new milestone button on the Roadmap page the path will be /milestone?action=new
and the user should have a good idea that the milestone does not yet exist (although it might be less clear when &name=milestoneX
is appended to the path resulting in the milestone name input having text).
In the case that a link is followed to a non-existing milestone the path will be /milestone/milestoneX
and it might be less clear that the milestone does not yet exist. We could give a clear indicator in this case:
The patch would be simple, and would not add a notice for the case that was first described, when the user follows the Add new milestone link.
-
trac/ticket/roadmap.py
commit 97d3d7d9c4be58309aa696474bf45dd5a749a605 Author: rjollos <ryan.j.ollos@gmail.com> Date: Tue Jul 1 10:23:37 2014 -0700 Add notice if milestone doesn't exist. diff --git a/trac/ticket/roadmap.py b/trac/ticket/roadmap.py index ab4c41d..bb53ea5 100644
a b class MilestoneModule(Component): 860 860 data['milestone_groups'] = group_milestones(milestones, 861 861 'TICKET_ADMIN' in req.perm) 862 862 else: 863 if milestone.name: 864 add_notice(req, _("Milestone %(name)s does not exist. You can" 865 " create it here.", name=milestone.name)) 863 866 req.perm(milestone.resource).require('MILESTONE_CREATE') 864 867 865 868 chrome = Chrome(self.env)