[#JRA-1012] Project management improvements

JIRA

Project management improvements

Created: 25/Nov/02 07:05 PM Updated: 06/Nov/07 04:07 PM

Component/s:

Project Management

Affects Version/s:

2.0

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

JRA-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

~~JRA-1582~~ Scheduled release date for unreleased versions

This issue is related to:

JRA-425 Ability to attach documents to Project

Participants:	Adam Harvey, Brian Lalor, Gerd Gueldenast, Joe Bissen, Kai Bounin, Keith Brophy, Kevin James, Kevin Ross, Mark Fortner, Tom Miller and Willie Mora
Since last comment:	42 weeks, 4 days ago
Labels:

Description

« Hide

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

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Kai Bounin added a comment - 05/Sep/03 05:37 AM

I'd highly appreciate this!
maybe we could also attach files not only to the project but also to the versions. This could be used to publish released versions and patches for download

[ Permlink | « Hide ]

Adam Harvey added a comment - 10/Oct/03 10:39 AM

Our PMs would very much like to be able to store the release date of a version.

[ Permlink | « Hide ]

Mark Fortner added a comment - 29/Oct/03 09:11 AM

It would also be useful if we could have customisable fields for projects not just issues/issue types. We're currently using JIRA to capture use cases (it's a new issue type we added), and using that we're able to generate a lot of the project documentation including a functional design and a simple project plan.

One thing that would be very useful would be to have some integration between tool like jxProject (http://www.jxproject.com) and JIRA. This would make it easier to create more sophisticated project plans using JIRA issues. We currently don't have a way of indicating in JIRA resource availability, and we have a lot of developers splitting their time on multiple projects.

[ Permlink | « Hide ]

Brian Lalor added a comment - 20/Apr/04 08:28 AM

The ability to attach files to the top level of a project would be extremely helpful. These would be documents such as Statement of Work, Project Charter, etc. We really need to have this functionality.

[ Permlink | « Hide ]

Kevin James added a comment - 30/Jul/04 04:46 PM

Being able to attach documents at the project level would be useful. However, we're actually liking our current setup where the project's URL links to a homepage for that project in Confluence where documents can be attached or even better the documentation is in Confluence itself. Allows us to link issues directly with the sections of the requirements or engineering documents from which the issues (improvements/features) originated.

[ Permlink | « Hide ]

Gerd Gueldenast added a comment - 08/Oct/04 10:54 AM

Great Idea! Please do this!

[ Permlink | « Hide ]

Kevin Ross added a comment - 13/Jan/05 05:26 PM

I'm trying not to spam several issues with this comment, but it seems like a recurring them. It seems that a methodology based management tool could be a separate add-on/integrated very easily.

Here are my ideas:

http://confluence.atlassian.com/display/JIRACOM/Meta+issues?showComments=true#comments

I would be interested in a planning software that has features like versionone.net. It's a great tool but I just cannot seem to part with the ease, flexibility and usefullness of Jira.

[ Permlink | « Hide ]

Keith Brophy added a comment - 16/Mar/05 10:11 PM

From the orignal description, items 1 and 2 are now done. Item 3 is still outstanding and will be reviewed for a future release.

[ Permlink | « Hide ]

Willie Mora added a comment - 28/Dec/06 11:13 PM

1. Going one setp further - it would be nice to just import from MS Project - it would be even nicer if we could identify what fields we wanted to export.

2. You already have a broadcast banner. It would be nice to have a project banner to alert team members of important project information expediently without being brocasted to all JIRA users. You could just add a drop down to the current banner that allows message visibility by group or project.

[ Permlink | « Hide ]

Tom Miller added a comment - 05/Nov/07 11:08 AM

I would prefer a link to a confluence page to put all my documents. I would want the page, links, etc. to display in Jira, not just a link.

I also would like to see more dates at all levels of Jira: project, issue, sub-task.