Concourse & Jira DC Portal
Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
hey all - this issue has been open for some time, and in this window we've made improvements to performance and stability, is this still an ongoing issue for team members?
The tool is too slow and need to reduce latency in order to increase our efficiency.
Hi, I believe that this is a great tool and very useful for our team, however the speed needs to be dramatically improved to drive efficiency and time management for users.
Hi there! Thank you so much for submitting this idea and leaving comments! We really appreciate the additional context and details! We're currently working on triaging this idea and assigning it to the appropriate team. As we begin to explore this idea, we'll stay in touch! Thank you again!
Hello! I am a US AC team member and I use Concourse often. The time spent waiting for data populate isn't efficient and dramatically cuts on productivity. The bandwidth for the application should be investigated and repaired as soon as possible.
I know that stability and the speed of Concourse are gradually improving. Unfortunately, I don't think it's happening quickly enough. In the US, my team members are waiting up to 10 minutes for Concourse actions that ought to really take 1/4 of that time. For the other half of my team in Europe and India, their key working hours are hampered by an even slower experience during site maintenance time. In the western hemisphere, we need more speed. In the eastern hemisphere, we just need to be able to do some work on Concourse.