Even if you put in the bare minimum, creating issues is a tedious process at best. And the most painful part was always populating those plans in Jira by creating issues. At the time, I was helping people across the company plan large projects. It was my job to run the entire instance, not create issues for him. That was the last straw I had to have an intervention with his manager. However, this Program manager thought he could abuse this and once turned in an excel sheet of twelve Epics. The company had used this process for some massive projects we were planning. It had gotten out that I could bulk import issues from a CSV file.
Storyo appreviews update#
I mean, seriously, did he want people to update Jira issues all day, or did he want them to do their actual jobs? At one point, it had ballooned to the point where creating a single epic would auto-create over 100 other stories and subtasks.īut his loathing of creating issues didn’t stop there. I’d coach him to have good Confluence documentation for the tiny little steps for each story and keep it high level – and he’d keep fighting me.
However, he kept wanting to add stories and subtasks.
We had set up some rules in Automation in Jira to create children stories upon creating an Epic.
His team was responsible for setting up servers and shipping them out to be installed at data centers worldwide. The problem was that he also didn’t trust his team to know what they needed to do. At one of my previous jobs, I had a program manager who hated to create issues in Jira.
0 kommentar(er)
