Concourse & Jira DC Portal

Hello Codie, voters and commenters, while the age of this request shows that it is related to Concourse Native, we wanted to provide some direction for support in Jira Cloud before closing this out. The 'Workstream' field in Jira Cloud is a single select field however, by default you also have a secondary field 'Dependent Workstream' field which is multi-select. Please utilize this as the best option for setting multiple workstreams on work items. Closing this Idea out. If anyone has specific Jira customization requests for your team, remember you can submit a JSM ticket. Submission links can be found here: Submitting Feedback Thank you.

Hey Klinttin, I'm sad to say that we haven't progressed on this feature or much of what is listed in our idea portal. Concourse is developing toward a goal of a global rollout this spring and it has consumed nearly all of our development capacity. Comprehensive research and planning has been done against this request and it's listed as a top adoption killer for the platform in our backlog. I'll be sure to post here again if we're able to commit this to build.

What's the status of this?

Thank you for submitting this idea - 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. They recently released this survey to gather additional feedback. If you haven't already done so, please respond to the survey so we can move this idea forward! Thank you in advance!

To expand on my previous comment here are two use cases:

1. RAID item use case - lets say we have a decision out for whether or not we want to enforce timecard entry for doctors (always a contentious topic) that decision needs to be made by the timekeeping team, but it will directly impact HCM and Payroll so all three workstreams need to be tagged on the decision for visibility. We have hundreds of RAID items so I can't expect teams to review things that aren't tagged to them

2. This same concept can be applied to our deliverables as well. One example would be Prototype 1. That is a deliverable, but if I was forced to actually assign it to only one workstream I'd need 4 deliverables in Concourse and Jira for HCM, FIN, SCM, & Payroll. This would exponentially increase our deliverable listing in Concourse, and wouldn't be contractually accurate

This would be one of the most helpful things conceivable for the integration with Jira. Right now we have half a dozen projects using work arounds and inconsistent workstream fields to be able to accomodate the necessity of multiple workstreams. As Concourse rolls out the RAID log this only becomes more necessary.