Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
Our subtask process is as involved as creating a new story. No data is autopopulated in the create a subtask or create a bug screens like TPAs, epics, components, sign offs, etc. We are going to start tracking work effort and creating the subtask is a huge hinderence. I have to put in a request with our system admin and I would like to have the steps to do this included with the ticket to help speed along this actually being done. I want to streamline the process so I only need to enter Title, assignee, description, and work effort when creating a sub-task or a linked bug. Basically if I am in a story and click create a subtask, I'd like the important info autopopulated on the backend, only new necessary fields shown to the user to be filled out and on Create show the new subtask in the subtasks section on the story.
There's two approaches to this
Second, the easier way - only place the fields you want the user to fill in on the "create subtask" screens and then find/write a post-function that can set the others and put it on the "create" transition
I think you need the second one, that will keep it really simple for the users. I'd use the Script-runner add-on, but there are other add-ons which can "copy data from parent issue fields"
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
As a Jira power user, I was at first doubtful that Trello could benefit my workflow. Jira already uses boards (ones you can customize!), so why would I even need to use Trello?! In this post you will...
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