|
[
Permlink
| « Hide
]
Lauri Siljam?ki added a comment - 29/Jan/04 03:38 AM
You should enable custom fields also on user objects. We would like to store secondary email addresses, phone numbers, product details etc. with or atleast attached to the user data.
This is a very interesting feature. Especially the possibility to add properties to a project would be very helpful for Core-Production methodology.
Regards, Would versions also be covered by this Feature?
When will this issue be implemented?
We have not yet decided if or when this will be implemented. I'm told the custom field system is flexible enough to allow it without major refactoring.
I'd like to have some tool that compares the approved budget (in work hours) of a version with the aggregated actual data obtained from the issues in that version. The idea is to detect budget overruns early, the tool could for example be implemented as a report plugin.
The natural place to store the approved budget seems to be the version, so like Markus I'd like to see custom fields for versions. In http://forums.atlassian.com/thread.jspa?threadID=6836&tstart=75 I think this would work, but it seems too much of a maintenance burden for me. I'd have to change the original sources of ManageVersions and EditVersionDetails, and keep track of those in all future releases. Plus if Atlassian ever implements custom fields for versions, I'd probably have a data migration problem. Has there been any movement on this one lately? We really need custom fields on versions and projects. I'm willing to offer bribes if you like.
Jeffrey,
We don't have any plans to implement this yet. You would be best off implementing this yourself as new tables in a database, managed outside JIRA. A great limitation on the customer reports that I create is that I can only use the data that JIRA wants to store. I'd really like to be able to save the following additional information on JIRA so that my JIRA custom reports would really work:
1) I'd like to specify the amount of person hours budgeted for a version/project. I'm sure many other people out there have their own requirements too. The point is, JIRA's extensibility is hobbled by the inability to add custom fields. We don't expect Atlassian to add on the specific fields that each of us would like - that would really pollute the domain model, and make things lose their shape. So the per-installation custom fields solution seems to me to be an elegant solution. If you add up the votes on this and JRA-1991 (and the many duplicates that are out there) you can see this is a highly sought after piece of functionality. (Incidentally - do you guys have a way of aggregating the unique votes for a cluster of duplicate issues? This would really help you see what your customers really want). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Custom fields all JIRA objects
