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

Key: JRA-4812
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Frank Schimmel
Votes: 15
Watchers: 10
Operations

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

Would like to provide default values of system fields

Created: 06/Oct/04 10:50 AM   Updated: 26/May/08 05:53 AM
Component/s: Administration
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: andrew hurst, Cherly Diaz, Dmitry Beransky, Frank Schimmel, James Kleist, Olle Friman, Owen Fellows and Scott Farquhar [Atlassian]
Since last comment: 37 weeks, 6 days ago
Support reference count: 13
Labels:


 Description  « Hide
I would like to provide default values not only for custom, but also for system fields.

An example:
Depending on the issue type, I would like to provide different default values for the field "Description" which help users to fill in e.g. the details of a bug issue.

Regards
Frank



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Owen Fellows - 06/Oct/04 02:58 PM
You could add some code to
/includes/panels/issue/create_fields.jsp
to give default values.

This is a work around until this feature is implemented.


Cherly Diaz - 05/Jun/06 04:44 PM
Hi,

I'm using version 3.6.1. I couldn't find the file specified above: atlassian-jira/includes/panels/issue/create_fields.jsp for this workaround. I'm guessing this work around is outdated? Is there another workaround for version 3.6.1 available?

Thanks!
Cherly


Scott Farquhar [Atlassian] - 05/Jun/06 09:55 PM
Cherly,

In newer versions of JIRA, each field has its own template. You can find these in velocity files (*.vm). You should be able to edit the files you want, and then restart JIRA for your changes to be picked up.

Cheers,
Scott


Cherly Diaz - 06/Jun/06 05:12 PM
Thanks! I was able to edit the field as needed

andrew hurst - 13/May/07 02:55 AM
In addition, it would be good to have default values associated to a Field Configuration so that you can different default values depending on the project / issue type

Dmitry Beransky - 16/May/07 04:16 PM
exactly, the default value for Description for a bug would not be the same as for a new feature.

James Kleist - 12/Sep/07 09:31 AM - edited
You can also add javascript to the description of the system field such as:
<script language="JavaScript">
if ( document.getElementById("description").value == "" )
     document.getElementById("description").value = "h3. Steps to reproduce\n# Step \n# Step\n# Step\n\nh3. Expected behavior\n\nh3. Observed behavior\n\nh3. Frequency of occurance\n\n";
</script>

Olle Friman - 01/Nov/07 03:03 AM
Is there any disadvantages by using James javascript suggestion above? It seems to work exactly the way I want and it can also differ for different Field Configuration Schemas.