-
Suggestion
-
Resolution: Obsolete
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
A few suggestions that I think would improve JIRA from a general project management perspective (and I think they are probably easy to implement to boot).
1. A 'estimated close date' or 'due date' field for issues (I think this may already be on the list). Would allow for some basic over/under schedule type metrics.
2. 'target date' and 'release date' tracking on versions (again simple scheduling metrics).
3. It would be very useful to be able to attach documents to the project itself, not only to issues. Often a project has high level documents (project charter, licensing docs, coding conventions, etc) that need to be in a highly visible, easily accessible location. Creating bogus issues to attach then to doesn't work so well (out of sight, out of mind). It would be great to be able to attach them directly to a project and have them listed on the main project detail screen.
Thanks,
Joe
- is related to
-
JRASERVER-1012 Project management improvements
- Closed
- relates to
-
JRACLOUD-13362 Allow JIRA issues to be scheduled based on either Issue Due Date, Issue Start Date, Version Due Date, Version Start Date, Linked Due Date or Linked Start Date
- Closed