Josh Hammond Expert

I second @Darryl Lee's request.

@Dushyant Sharma are you able to share how "journeys" will either be integrated with automation or differentiated from automation? It seems like journeys are a simplified version of what many teams currently use automation for?

Hi @Betty Sheu . My enterprise team and I have so much feedback and questions for you regarding user-generated access and app requests. :-) Would it be possible to schedule a call to discuss?

I'm seeing a lot of piling on today... Key Themes * The communication was not clear (not everybody understands what "unique constraints" means) * The implementation timeframe seemed too aggressive (two weeks isn't enough time for everyone) * The instructions were lacking actionable insights (now we know we have a problem…

@Sebastián Durán here is the open feature request: https://jira.atlassian.com/browse/JSDCLOUD-3952

@Alonzo Kennedy - I was looking for the same thing. Here you go! https://jira.atlassian.com/browse/JSDCLOUD-3952

I'm also interested in the answers to the questions that @Matt Richards raised. For my team, the most important question is how Atlassian will handle the reconciliation of the Atlas "Project" and a Jira "Project" concepts. Maybe one is Project and the other is project to avoid user confusion? 🙃

Thank you, @Tina Ling ! You all are off to a very productive year. :-)

@Kevin Minnick are there any plans to send Atlassian audit data into Analytics? When I first read the title of your post, I thought that dream had come true. :-) Still, this is a welcome improvement to have audit activities in one central place. Kudos to you and the team!

Just stumbled onto this thread. Really like the suggestion! Has anyone seen any JAC requests for it?

Hi @Tina Ling * It's nice to see these fields being made available, especially since they're getting sent over through the data share as part of the initial release * The recent posts from the Analytics team regarding new field availability have been top notch:* Very clearly communicated * Helpful instructions and…

@Vilmos Varszegi I stumbled onto your post a bit late, but it seems like this feature request might provide something along the lines of what you're looking for: [JSDCLOUD-4445] Ability to hide Create button based on project or signed in users group "We have a project in which we want people to create issue via the Service…

One other troubleshooting step to mention for anyone still experiencing issues is to see if there are any fields in the queue that are showing as read only (heading not bold). I ran into an issue where Request Type was not editable and because it was listed in the queue, the queue appeared to be read-only.

Adding a link to Part 3: Collaborating with Lighthouse Users: Jira Product Discovery Case Study

Hi again, @Carol Jang . Are there any intentions of enabling non-scrum teams to be able to use the Program board (or something similar)? For others, being able to plan in other increments (e.g. months, quarters) could also be quite powerful and eliminate the requirement of using sprints.

Hi @Carol Jang . Thanks so much for adding the helpful images and descriptions. Our team will be very interested in these features.

Hi @Carol Jang . Those are great additions and I'm looking forward to the new AI feature. Do you have links to more information (e.g. announcements, KB articles) for those releases?

@Janne Toivonen you raise an interesting use case. Essentially, you'd be subdividing a portal into multiple help centers based on topics / categories (i.e. access requests)? It seems like the value in this approach would be that the UI for portal customers could be tailored for specific topics while the back-end (including…

Thank you for the prompt update and your team's efforts to incorporate this functionality, @Raafi Mohammed ! The recent Help Center features are unlocking a bunch of helpful solutions for our organization and driving increased user adoption.

Hi @Raafi Mohammed. This new functionality is excellent! Kudos to you and the team for implementing it. We would like to see the ability for projects to be unlinked from the Default help center. Currently: All the projects in your site are always linked to your default help center, the resources will always be available in…

This is great news. Thank you, @Claire Gayrard

Hi @John Funk. You can list the Atlassian Community as the referrer if you haven't completed the application already. Thank you for your interest!

Hi @Aaron Rowsell Thank you for reaching out. We are looking to hire permanent full-time employees for these roles. Interested candidates can apply directly via the link above.

Thank you, @Akshay Johri ! Looking forward to trying this.

Hi @Akshay Johri . Is this EAP open to organizations that are fully cloud-based? The portfolio insights seem like they could be helpful for cloud customers looking to better view their technical landscape at a glance.

Hello. I see that this feature is GA but is it still being rolled out to organizations? Ours does not appear to have the options available that are described in the documentation and we're on the continuous release track.

@Thibaut Julien_Elements-Apps_ all excellent observations! I would also like to see a way to determine whether new projects are automatically added to all help centers (or not). Right now, we have to remember to manually go into every help center to hide a new project that only applies to one or two help centers.

It's great to see this feature available! Feature parity between MS Teams and Slack on the Atlassian platform is appreciated.

Thank you, @Bill Sheboy

Is anyone aware of a feature request to make this important "team" field available as a field to edit in automation? The workarounds above are very helpful, but an admin shouldn't have to go through all the hassle to do something like this.