You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag.
Do you structure your teams in a certain way? Do you take a unique approach to estimating? What’s your approach to using releases? Do you take advantage of a particular report? Share your thoughts with the Atlassian community!
They're going into spam.
One of the spam filters is "was the same text posted very recently", so once your first post is filtered, attempts to re-post it are pretty much automatically filtered too.
Anyway, I have yoinked the last one out of spam, it should stay now!
Committing Plan Changes
Multiple Scenario Planning
Leveraging Target Dates
Re-prioritizing work items
Stages and Skills
Working hours and days
Using the timeline
Creating and managing releases
Excluding releases from your plan
Using the later release
Excellent !! @Cameron Eldridge, how would you sort this problem? https://community.atlassian.com/t5/Portfolio-for-Jira-discussions/How-to-add-maintenance-sprint-in-the-plan/m-p/837992#M111. Sorry to ask directly, but I doubt that any new user can help and you look to have so much experience, that I believe it's a case that you might have faced.
I've added a comment to your other inquiry.
Here are some instructions to create and configure an Initiative Kanban board.
CREATE A KANBAN BOARD
1. Select Boards > View All Boards from the top navigation bar.
2. Click Create board at the top-right of the page, and choose to create a Kanban board.
3. Click Create a Kanban board, then choose to base your board on an existing project.
4. Follow the prompts to set up your board. Your Kanban board will have a default filter. Modify the query as shown below. XYZ will be the key of your selected project.
project = XYZ AND issuetype = Initiative ORDER BY Rank ASC
5. Congratulations — you have created a new board! Now it's time to configure your board.
MODIFY THE CARD LAYOUT
1. Navigate to the board's Card Layout tab via Board > Configure > Card Layout.
2. Add the Fix Version/s field to display the release your Initiative is planned for. If you use Portfolio 3.x, you may also want to add the Target start and Target end fields. Alternatively, include meaningful custom fields you leverage in your instance for Initiatives.
1. Be sure to configure your board columns relative to your Initiative workflow statuses.
2. Configure your Issue Detail View so that you have quick visibility into pertinent fields.
3. Add Quick Filters to narrow your board results. For example, add a "Current Release" quick filter to see Initiatives in your next planned release. Include your project key (XYZ) to speed up the query.
fixVersion = earliestUnreleasedVersion(XYZ)
@Cameron Eldridge Can you elaborate on the following:
Multiple Scenario Planning
I am particulary interested in the Release Shift scenario. Assuming this allows you to take a baseline of your plan and then the ability to see changes in the Live view of the plan and how they differ from the baseline ??
The data flowing into Portfolio is dynamic, so there's no way to snapshot data within live plans. Release Shift could be used to assign issues to earlier or later releases, re-rank them, and calculate the changes to see shifts in the Schedule (timeline) view.
You could also swap to the Target schedule view if you've previously set Target start and Target end dates to compare against the shifted release dates.