I joined as a entry level JIRA admin in my company, whenever a deployemnet request is needed, the devloper has to create an issue in jir and give some extra details than the default ones. So, is there any way in JIRA that we can create a deloyment issue template, so that whenever a developer would like to create an issue it should give option to choose deployment template and fillout the extra things needed.
Nope, the whole point of the "create issue" function is that it asks the user for information that is needed later. If the information is fixed, then you don't actually need it entered.
You can set up defaults for most fields, so that the users doesn't always have to select from them, but the templates you describe are not really possible. (A better option is to drop all the fields that depend on something and populate them using post-functions after they commit the new issue, but for complex cases or if/thens, you need code to be able to do that, and you can't do that on JIRA Cloud)
rather than a blank issue description, it would be helpful to define a template of the structure of a story. For example we have defined Definition of Ready with several key sections that need to be filled (Story, Definition Of Done, Acceptance Criteria, etc.) Also, we would like to use markdown to format this outline. It is innefficient and inconsist to have each person fat-finger these in from scratch each time. As a Product Owner, I want a story template in JIRA to fill in the initial structure, then have the story writer fill in the specifics.
This is legitimate feature request.
ok, may be i told wrong its not issue its a task that developers give to the deployment team, basically developers don't give all the information at a time, they just give if deployment team asks for or they give it like sctattered. So, our intention is that whenever they create the task, they should be able to see few more fileds like
a)path of the war file
b)path of the license file
c)version of the software etc
Break up your issues into issue types. If, for example, the one you've now detailed here is a "deployment request", then have an issue type called that. You can then associate those custom fields with just that issue type, and the users will on;y be prompted for the relevant fields when they select the right issue type.
Another alternative is to look at the facitilites that JIRA Service Desk provides for these sort of service requests. You can then map different request pages to different types of request but still deal them with them in JIRA as the same issuetype but having made sure that you have captured the correct data for that service request.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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