I'm creating a ticket issue for travels. Users usually have multiple trips which require them to check-in to multiple hotels, flight to different planes to move to different locations.
You need to look into available plugins if that is suitable but out of the box there is no functionality to enable more fields on a button. You could look into creating a screen on transition but that is when you use JIRA internally.
Keep in mind custom development is not the best approach for the Cloud offering.
Thanks Nicklas. We're using it internally. My problem is if i create 3 sets of fields for hotel ( 1 field for hotel name, 1 field for checkin date, 1 field for check out date ), that will make my ticket form too long. In addition, the fields for air travel which consist of 3 fields as well. If I create another 3 sets of field for the airplane, the form will be as long as could ever be.
Out of curiosity what is your current process (without JSD)? Does the user email their desired itinerary to you to be processed / approved? In such case you can start by providing just a text area. I know it's not optimized to structure the itinerary item, and has no city / date picker etc but at least you benefit from JSD's SLA, queue, workflow and approval.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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