We are looking for a solution to help ensure groups across our organization stay coordinated on deadlines and plans, and we believe Team Calendar can help accomplish this; however I'd like to understand what the best practices are for tracking milestones within JIRA. On the Team Calendar product video it appears to add JIRA calendars that contains milestones for projects, so I wanted to know what the best practices are for doing this. In some shots it looked like different date fields were used, but in other shots it appeared like different issue types were used - so I couldn't tell what the recommended practices were for different situations. As with all of your products this appears very configurable so I'm sure there are multiple ways of tackling this, but if possible we'd like to take advantage of the experiences and knowledge that others have already had with this product to understand the best practices.
@Darren. Yep you're right.
So with JIRA, you can create custom types for issues (see https://confluence.atlassian.com/display/JIRA044/Defining+'Issue+Type'+Field+Values for details). What we see plenty of teams do is the following:
* They use JIRA versions for release planning (set a due date for a release and it appears on the calendar)
* They create their own types of issues to represent their processes (E.g. "Scheduled Deployment" or "Outage" or "Change").
* On those JIRA issue types, they use the out-of-the-box due date JIRA provides, or create a custom date field of their own (see https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field to learn more about cusotm fields). So they would create fields like "Outage Start" and "Outage End" or "Deployemnt Date" etc...
* In Confluence Team Calendars, they would create a JIRA event type and select those things (JIRA version dates, issue daue dates for their custom fields etc...)
Hope that helps explain it a bit better? Interested to hear how you went.
I know I'm VERY late to the party, but iIve been creating a custom issue type called "Milestone" that includes custom fields for start date, planned end date and actual end date. The workflow contains statuses for on track, at risk, past due, and complete. And I just like that milestone to individual tickets to indicate dependencies. This way I can run reports and what milestones are coming up, plot them on a the team calendar and see "pileups" coming in advance, as well as send notifications to affected team members automatically. This helped me get around needing more specific dates tracked and reported outside the fix versions, and cope with some of the waterfall-y requirements of portfolio management while still using scrum and kanban boards to manage software. It's also great for business projects :)
@Marisa Hager Hi Marisa! And what do you do with stories, tasks and sub-tasks that are assigned to this milestone? You just do a simple link between a milestone and a story/task/sub-task? Or something more sophisticated? (For instance, the milestone is a parent issue of a story)
@Naveh so sorry for responding so late! Fwiw, I just use links between milestones and what they impact. You can customize the link types to indicate all kinds of dependencies or relationships and then report on those specific link types. But there isn't a hierarchy - like the way tasks are parents of sub-tasks. You can see what milestones a story or task is linked to, and query the type of link ("requires", "relates to", "must finish before" etc.).
@Abe Saeed . The key is just understanding how you want to organize your work. In a lot of cases I absolutely leverage epics - I can either give them due dates and plot them on the calendar, or just organize them into fix versions and put the fix version on the calendar. I tend to use the milestone issue type for stuff that is outside of coding or releasing. Things like when will hardware will be delivered and racked (milestone)- and will it be ready in time for our product code rollout (fix version). Or when do we have a special integration demo for clients at the industry conference (milestone). Or when will the waterfall team that we're depending on (that doesn't use Jira) deliver the piece we need to make our epics work? Things like that. So in that sense I define an epic as a group of related stories that is no bigger than a release cycle. I use fix versions for the epics to indicate which release they're going to production in. And then I use milestones for all the ancillary stuff (hardware availability, end user documentation handoff, marketing brochure copy delivery, integration with an outside/dependent team, etc.).
Thanks for the question and for the feedback. We are trying to make it more obvious what the best practices are in the product, so this is very helpful feedback. Regarding your question:
* Use JIRA versions to plan a release
* JIRA versions can have a due date, when you set the due date it will be ready to appear in Team Calendars
* In team calendars create a JIRA calendar and select "Version due dates" to display
* Now dragging and dropping your JIRA versions from Team Calendars will help you reschedule your release. Your team can watch the JIRA calendar and get notified when the release date is changed.
Is that what you are after? There are a few issues we'd like to improve here:
would love to hear if that works for you
That is along the lines of what I'm looking for, but more specifically I'm trying to understand the best way to handle situations like in the product video where there are JIRA calendar items for things like product launches, integration dates, etc. I'm pretty sure these aren't all versions, so I was curious what the recommended way of capturing these types of items were?
Hi Community friends, We're working on sourcing more reviews on Capterra – a popular software review site – to help teams like yours make more informed decisions when choosing an inc...
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