In our enterprise roll out of service desk we've run into scenarios where requests have multiple sub-tasks or components that relate to the the parent task. For instance if you are moving a series of workstations or installing to multiple locations for a whole team. This would be easily accomplished if the requester had the ability to add sub-tasks to the the main task. Each sub-task might include a workstation ID, Hostname, user, new location... etc. Jira is absurdly flexible when it comes to issues and the fields supported but the only way to make this happen is to provide access to the full Jira interface which is defeats the self service model. Has anyone else run into this situation and how was it overcome?
Hello there Cloud Community members! Today, we’re thrilled to announce Jira Service Management, the next generation of Jira Service Desk. Jira Service Management touts advancements in IT service ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events