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.
2. Thanks. I'll let our devs play with the config-as-code a bit more and provide feedback.
4. Yep, or even just typing in a JQL and then saving it without having to create a new filter. Either way is fine.
Hey @Dan G @Leonard M I hope you are both doing well. I wanted to follow up on #4 with Jira Software.
Short answer: You can use JQL with the component field as you would any other field, which cuts across projects. So "all issues with component 'auth-srv' AND status 'to do'" could be a query to track technical debt across various software components being tracked in Compass.
Ok, so couple of caveats
Long-term we plan to fix all of this by making the native component field be used specifically for Compass and tracking technical architecture, which can then be used to map work <-> architecture <-> teams very easily with all the power of JQL and Jira behind it as well as all the new Compass search, dashboards, & reporting - eventually having it's own JQL equivalent.
We are currently working on improving our Jira Software integration by creating our own custom field, that will automatically populate the Compass components as the available options when selecting values on a Jira issue. You can then use this custom field in JQL as you would expect. This is blocked by some internal dependencies we hope to get removed soon.
You can read more about that here. https://community.atlassian.com/t5/Compass-Alpha-articles/POSTPONED-A-brand-new-way-to-track-Jira-issues-against-Compass/ba-p/2096414.
Hope that adds a bit more context for how we expect teams to use JSW + Compass together, which I believe aligns with how you will want to use it.
Hi @Dan G
Thanks once again for the feedback - like Andrew said, a Monday morning gift indeed!
We’re currently running research looking at the admin onboarding experience on Compass.
Would you or someone in your organisation be willing to share your experience with us? It will be a 45 min call on Zoom.
Please pick a time that works well for you - https://calendly.com/atlassianresearch/compass?month=2022-07
If the time slots don’t work, let me know and I can find another time that suits better.
Yes, let me pass this to the person running most of this now, he'll get more feedback over the next 1 to 2 weeks, then I think it's a good time to schedule.
That would be amazing, thank you. I'll add more time slots in there for the next couple of weeks for them to book in.
I am helping Dan G with the process of onboarding Compass. We should need another week to get all our feedback together. Once completed I will let you know.
Hi @Leonard M
Thanks so much for the heads-up. I look forward to speaking with you and getting your feedback.
I am trying to add more feedback but I am getting the below error.
You may have recently posted the same thing elsewhere on the community. Update your text, or wait before reposting.
I have tried to wait and change the text, but nothing seems to help.
Hi @Leonard M
Sorry, you had that issue. Thanks for letting us know. I checked with the team, it could be because the message is longer than the allowed character limit.
We could do one of these three things:
Thanks again for taking the time to thoughtfully write up your feedback. I'm looking forward to it.
Thanks for coming back to me, I tried splitting the feedback but I received the same error message.
So I have booked a zoom call with you.
Oh no, I thought that would work. I'll check in with the community team again, it could be a different issue altogether.
Glad you booked some time, thank you for doing this.
Looking forward to the call!