History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-6041
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Duplicate
Priority: Blocker Blocker
Assignee: Unassigned
Reporter: Prakash Sannapu
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
JIRA

Ability to add and filter custom fields at the project level

Created: 24/Feb/05 06:37 PM   Updated: 04/Mar/05 12:51 AM
Component/s: Custom Fields
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Reference
 

Participants: Prakash Sannapu and Scott Farquhar [Atlassian]
Since last comment: 176 weeks, 2 days ago
Resolution Date: 04/Mar/05 12:51 AM
Labels:


 Description  « Hide
Hello,

We are currently considering purchasing Confluence & Jira for our organization. I've been playing around with JIRA and quite happy with its functionality. However, our leadership requested a simple feature which I've noticed is lacking in JIRA. i.e Being able to add custom fields at the project level, just like the way JIRA adds at the issues level. This helps the management to track the project level status/risk/phases etc. I think this would be a killer improvement to Jira. As business people can then filter on custom fields at the project level while the techies can contiue using the issues level filters as it is available today.

I could actually create custom fields throug Jelly and import data for those fields. In fact I can even import data into custom fields through CSV import into a project while creating multiple projects on the fly. I've tried this and it works. However, when I try doing a filter at the project level through dashboad. I am not able to retrieve any of that data I imported....I understand this being the fact that JIRA is focused at isssue level. I would sincerly appreciate if someone can get back to me and let me know if this is feasible for me to expect this improvement or not. Of course, this will decide wether we would replace Clearcase with Jira or not

Thank you
Jeffi
602-378-225(desk)
602-206-0271(cell)
623-332-3427 (personal Cell)



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] - 27/Feb/05 03:00 AM
Jeffi,

Project level custom fields will come in time - most likely this year. However, I can not promise an exact date for you.

If you are after a way to automatically assign an issue to the QA lead for the project, you can create a workflow post function to do that? It is quite simple java coding.

Let me know if that would work for you?


Prakash Sannapu - 02/Mar/05 12:34 PM
Scott,

Thank you for the response! I am not after automatically assigning an issue to a QA lead. Rather, I would like to be able to add few custom feilds at the project level for example, Project Sizing, Risk, Status, Business Unit, Business Proponent etc. and then create filters on the added custom fields. So that when our Manager logs into the JIRA, he would be presented with Project level filetered information rather than showing the Issue level details. As Manager's are more intrested in abstract data than details. This would a killer feature to thrill any Manager on selling your tool.

Tuust me I've used many tracking solutions and none are close to achieving than JIRA. In fact, JIRA is so close that it has all this done at the issue level. I am surprised to see why my hands are tied to do the same at the project level? As a programmer I do not see it being a big issue, it should be relatively easy to address

Jeffi


Scott Farquhar [Atlassian] - 04/Mar/05 12:51 AM
Prakash,

As you get JIRA source with your purchase - please feel free to address this if you wish

Project custom fields will happen in time, along with a whole host of other features that users are asking for. Unfortunately I can't give you a definite timeline on the implementation.


Scott Farquhar [Atlassian] - 04/Mar/05 12:51 AM
As this is essentially a duplicate issue - please add comments to the linked issue instead.