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

Key: JRA-1871
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Mike Curwen
Votes: 13
Watchers: 2
Operations

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

Custom Issue Types + scope

Created: 19/Jun/03 05:36 PM   Updated: 07/Jun/06 11:11 PM
Component/s: Administration
Affects Version/s: 2.2 Pro
Fix Version/s: None

Time Tracking:
Not Specified

Environment: WinXP, TC4.1.124, mysql
Issue Links:
Duplicate
 

Participants: Mike Curwen and Owen Fellows
Since last comment: 265 weeks, 2 days ago
Labels:


 Description  « Hide
I've been playing with the 'new' (to me) custom fields feature. Very cool. Especially how you can scope them to 'global, per project or per issue type'.

We can also customize issue types, priorities and resolutions.

I was wondering if it's crazy to dream of a day when JIRA might allow 'scoping' of these built-in fields as well?

It would be very handy. We could open up our JIRA install to serve external customers that only wanted to have one issue type (IE: a complaint!)

I think with many end-customers, having to select amongst bug, task, inprovement, new feature is daunting.

And hey... while we're at it... the fields that appear on "the next page" like version, environment, assigned to, etc... Could those be configurable as well

Does it sound like I'm wanting JIRA to morph into a CRM-like application?



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Mike Curwen - 19/Jun/03 05:38 PM
Sorry, I realized I kinda only half-explained something...

I said: "Could those be configurable as well " (without a '?'.. grrr).

I meant by that:
if they choose 'bug' then the fields that need to filled in are:
a, b, c, d, e, f

but if they choose my custom issue type of 'complaint', then all they get is :
a, b, c and my custom fields called p,q and r

Yah, I don't want much, really.


Owen Fellows - 20/Jun/03 12:34 AM
There are some great ideas for features there and customisation of default fields is something we have already considered as some user wish to remove unused fields.

I'm sure we will be adding some of your feature requests into future versions of JIRA.

Thanks for the comments.