Concourse & Jira Cloud Portal
For many projects (e.g., PMOs), we have recurring milestones that we want to be able to track in Concourse. For example, a monthly budget forecast, a quarterly Board presentation, a weekly status report. Concourse does not currently have this functionality today, so we have to create each recurring milestone manually, which is very tedious.
One of the large engagement (Salesforce) reached out, and they need to duplicate recurring tasks by week for the whole year engagement. Currently they are doing it manually for hundreds of rows, but it would be nice to be able to mass duplicate tasks
Hi Brittany! Thank you for the additional details! We really appreciate all of the feedback we've received on this idea. It's been very helpful as we explore this. Thank you again!
To add on to this: the ability for users to "select recurring task" which would allow the line item to be mass duplicated by setting the number of times or an end date and cadence (e.g. daily, weekly, bi-weekly, monthly, quarterly, yearly).
Example, Status report for 12 weeks and the first line item has a due date of 5/7/23 and all future items also auto-fill the dates so Status report 2 would automatically put the date 5/14/23.
If using the Status report function, it should automatically create the line item, with date and attach that version of the status report for saving into Save It.
Need: We have so many projects that last over a year and creating 52+ line items is very tedious - most teams may be bypassing Concourse and uploading directly in Save It or only having one line item with multiple uploads (hard to track if completed).
Hi Eric! This is super helpful, we greatly appreciate you sharing this information! All of your comments have allowed us to better understand the problem statement!
There's actually another idea that we've started researching that I think you may be interested in as well CONC-I-523 It focuses on auto populating dates in Concourse which relates nicely to your comment around cadences changing. Feel free to check it out!
Thank you again for everything! We'll be in touch as we continue on our research journey!
Hi Courtney - virtually every engagement I have includes at least one recurring deliverable (e.g., status reports), but some engagement types, like the PMO I'm on right now, have a lot more. Pretty much every deliverable I manage today is recurring - status reports, budget digests, roadmap updates, Board reports, etc. The current Concourse layout makes managing all of this a heavily manual admin task, and if the cadence changes (which happens frequently), manually revising the dates on each line is very cumbersome. I would estimate that I could lose about 1-2 hours updating Concourse if I kept it accurate every time those dates change; instead, I don't bother to update that, which makes my Concourse less accurate.
Hello everyone! Thank you again for submitting and voting for this idea! As you know, we've started exploring this! As we do our research we'll be reaching out with questions! Here are a couple of things we would love to get some clarity on:
On average, how many recurring deliverables do you see in your engagements?
What percentage of your engagements include recurring deliverables?
How long does it take you today to create those recurring deliverables in Concourse?
Like I said, we'll continue to reach out and stay in touch as we have more questions. Thank you all again!
Thanks for the great idea Eric - we’re excited to see the interest it generated! We recently established a Concourse research team that is completely focused on exploring user generated ideas like this. Based on the interest in this idea, we are revisiting it and as such have changed the status back to In Review. Our Concourse research team will be in touch as they explore this idea further!
@Alexander Burr - Duplicating the deliverable gets cumbersome when you're doing it at high volume (e.g., 1x/2x per week for a year long engagement). Also, if the frequency or due dates change, which happens often, you have to manually change these dates on each cloned deliverable.
What would be the distinction between this feature and just duplicating the deliverable? Maybe what we could try is when you are creating your workspace you create your recurring deliverable and then you just duplicate for each time you expect to do that work item.
This has 17 votes - why did it get demoted to long term consideration?
Concur, these recurrings can be automatically added to every project in order to speed up the ramp and make it consistent & predictable for everyone.
Thanks for your comment. Duplication does not satisfy this use case. If I have to duplicate a weekly activity for the whole year, that means I have to manually adjust titles and dates for 52 separate rows, which is cumbersome.
Users can duplicate a given milestone / work item and use it across different stages of the engagement