I think I know the answer to this, but I just want to verify:
My company is using a server installation (7.1) with Portfolio, Tempo Timesheets, and Structure, in addition to the standard JIRA Software. While in Tempo, when I view an "Initiative" issue type, the hours for all the epics (and subtasks) I have placed under the issue do not display. I am assuming that this is because "Initiative" is really only "functional" within the "Planning" aspect of Portfolio, correct? If so, does this mean that if I want to display total hours I would instead need to just track against Epics and below within Tempo? Thanks!
Regarding Structure - we added support for Portfolio's hierarchy links (Parent Link field) in version 3.4 so you can now recreate your Portfolio Plans (Initiative > Epic > Story > Sub-task) inside structures.
I've written up the basic procedure here - Track Portfolio Plans in Real Time with Structure.
The integration is two-way, so you can move Epics between higher levels (Initiatives) by dragging and dropping in Structure, and the change will be reflected in Portfolio.
Hi Robert, great to hear that!
All the functionality is there. I hope to get it written up before the end of this week and I'll post a link here when it's ready.
The gist is - there are two main ways to do it:
a) a single structure containing a folder for each Plan, and simply repeating the procedure already described under each folder to pull the plans in, or
b) a structure for each plan and a separate 'master' structure, again with a folder for each plan but this time just pulling in the other structures using the structure Inserter.
The net result will be the same and I think the choice of approach will mostly come down to preference.
Thank so much. I've run into another small problem.
(Please bear in mind my last experience with Structure was when it was still drag and drop, the automations are new to me, plus everything 3.0 )
I have 3 filters, so I created a folder for each filter and then followed the instructions on the blog for each folder, but I just ended up with 3 copies. How can I pull each initiative into a separate folder?
It sounds strange that you should end up with the same contents in each folder if you configured automation in each folder for a different filter..
Putting individual Initiatives into separate folders (as opposed to putting Plans into separate folders) requires a different approach, building from Initiative level downwards. It's also the topic for an upcoming post but the short story long is:
The structure should now look something like this:
Now any time you put an Initiative anywhere in the structure (not just in a folder), it will get extended with Epics, Stories and Sub-tasks. Similarly any Epic or Story you add will also be extended all the way down to Sub-tasks.
As for getting identical results when you were trying to put different Plans in different folders, it sounds like something's misconfigured there. Could you send a screenshot of your automation for two different folders to me at email@example.com?
Hmm, an afterthought... you said "I have 3 filters, so I created a folder for each filter" - maybe this is the problem - for each Plan-folder, you need to pull in issues from the sources used for that exact Plan... does each of those filters represent the source for a single Plan in its entirety?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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