I can think of a possible way to do this in JIRA Cloud with a combination of custom fields + post functions offered by JIRA Suite Utilities add-on.
It would rely on you having JIRA Suite Utilities enabled in your Cloud instance, which is possible (for free). Read this thread for info about that.
When I get a moment, I'm going to set it up myself in a test environment and see if it works.
If it does, I'll post the steps here.
I found a non-scriptrunner solution works with the description field, if you have JIRA Suite Utilities (JSU) enabled on your Cloud instance.
These are the steps:
Now, when users create issues, they see the 'Default Description' field, pre-filled. They can leave as is, or edit. When they create the issue, the value is copied into the real desciption field.
To get different default values for different issue types in the same project is possible, but more work. It requires an seperate custom field with the default value for each issue type, and create screens and workflows configured accordingly.
Unfortunately, this approach doesn't work for summary, as JIRA validation requires the system Summary field to be on the create screen.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs