8 results found

1. Support for Image Attachments in Ava

   Please enable the ability to attach and analyze images within Ava, particularly for internal usage with the Archon client where customers often attach documents and screenshots to tickets. Currently, Ava does not support attachments, leading to suboptimal responses when users attempt to get help with image-based content. For example, when users tried to have Ava describe screenshots, it failed to access the attachments, while other LLMs like ChatGPT and Claude handled the same task more effectively.

   Given that the LLM backend (gpt-40) already supports image analysis, implementing this feature should be feasible. This capability would significantly improve Ava’s usability, especially for clients who frequently deal with screenshot to explain their issue

   Please enable the ability to attach and analyze images within Ava, particularly for internal usage with the Archon client where customers often attach documents and screenshots to tickets. Currently, Ava does not support attachments, leading to suboptimal responses when users attempt to get help with image-based content. For example, when users tried to have Ava describe screenshots, it failed to access the attachments, while other LLMs like ChatGPT and Claude handled the same task more effectively.

   Given that the LLM backend (gpt-40) already supports image analysis, implementing this feature should be feasible. This capability would significantly improve Ava’s usability, especially… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Single Email Login for Multiple Domains in DoIT Console

   Hello Bonjour dear Product Team,

   I am reaching out to suggest an enhancement to the DoIT console that would greatly benefit large organisations with multiple BUs, particularly those that have grown through acquisitions.

   Issue Summary:
   Currently, users must log in separately to each domain within the DoIT console to manage cloud resources and costs. This can be cumbersome for teams that oversee cloud management across various business units within a single company. The need to log out and log back in for each domain creates inefficiencies and complicates the management process.

   Desired Outcome:
   We propose the implementation of a feature that allows a single email address to be used for logging into multiple domains within the DoIT console.
   This feature should provide the following capabilities:
   - A unified login experience that grants access to all associated domains without the need to log out and switch accounts.
   - The ability to seamlessly navigate between different domains from a central dashboard, improving the efficiency of cloud management tasks.
   - Enhanced user permission controls to ensure that access to each domain is properly governed and aligned with organisational policies.

   Suggested Solutions:
   - Develop a multi-domain access system that links multiple domains to a single user profile, based on the user's email address.
   - Introduce a domain switcher within the user interface that allows users to toggle between domains they have access to without logging out.
   - Implement robust access controls that allow administrators to define and manage the level of access each user has for each domain.

   Impact:
   The introduction of a single email login for multiple domains would significantly improve the user experience for teams managing complex cloud environments. It would streamline the navigation process within the Navigator/DoIT console, reduce the time spent on administrative login tasks, and encourage wider adoption of the tool.

   This feature is particularly critical for organisations with centralised cloud management teams responsible for multiple business units. By simplifying the login process, we can enhance productivity and ensure that their cloud management efforts are more cohesive and efficient.

   I strongly believe that this enhancement aligns with DoIT's goal of simplifying cloud management and would be a valuable addition to our Navigator.

   Hello Bonjour dear Product Team,

   I am reaching out to suggest an enhancement to the DoIT console that would greatly benefit large organisations with multiple BUs, particularly those that have grown through acquisitions.

   Issue Summary:
   Currently, users must log in separately to each domain within the DoIT console to manage cloud resources and costs. This can be cumbersome for teams that oversee cloud management across various business units within a single company. The need to log out and log back in for each domain creates inefficiencies and complicates the management process.

   Desired Outcome:
   We propose the implementation of a feature… more

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Enhanced cost savings Insights and effort matrix integration

   Hello la Product Team,

   It would be very interesting to develop a feature that enables customers to prioritise their cost saving opportunities based on potential financial benefits and to assess these opportunities within an effort matrix for better decision-making alongside the Insight feature.

   Feature => Cost savings evaluation tool:
   It would be a complementary tool with Insights that allows customers to input data and receive an estimation of the financial benefits from the insights and recommendations provided.
   The tool should be able to differentiate between savings, spend reduction, and cost avoidance.
   The output should clearly indicate the monetary value associated with each recommendation to prioritise actions based on potential cost savings ($$$$).

   Effort matrix integration:
   You should integrate an effort matrix that positions recommendations within a framework that compares the required effort against the anticipated benefits.
   The matrix should include an estimated cost savings metric to visualise the trade-off between effort and financial gain.
   or
   Develop a metric or scoring system (e.g a difficulty level from 1 to 10) to quantify the effort required for each recommendation.

   FinOps cultural adoption:
   Enhance the insight feature to promote the FinOps way of thinking, incorporating appropriate terminology and concepts.
   Tailor communication within the tool to effectively address different personas, ensuring that the messaging resonates with their specific interests and triggers the identification of needs.

   User impact:
   This feature will empower customers to make well-informed decisions by providing a clear understanding of the cost saving potential and the effort required to achieve those savings. It will also facilitate a deeper engagement with the FinOps culture, leading to more strategic and efficient financial management within their organisations.

   Additional notes:
   The feature should be user friendly and accessible to individuals with varying levels of financial expertise.
   Consideration should be given to how this tool can integrate with existing insight feature and analysis workflows.

   Merci !

   Hello la Product Team,

   It would be very interesting to develop a feature that enables customers to prioritise their cost saving opportunities based on potential financial benefits and to assess these opportunities within an effort matrix for better decision-making alongside the Insight feature.

   Feature => Cost savings evaluation tool:
   It would be a complementary tool with Insights that allows customers to input data and receive an estimation of the financial benefits from the insights and recommendations provided.
   The tool should be able to differentiate between savings, spend reduction, and cost avoidance.
   The output should clearly indicate the monetary value associated… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering More Feedback  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Getting Started Office Hours Notification Banner

   Hi Product Team - We have an underutilized offering in Navigator that all customers have access to. We are seeking a way to drive more registrations to the DoiT CSM Getting Started and Office Hours webinars in Livestorm.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering More Feedback  ·  3 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Enhanced Multi-org Email Notification Management

   Hello Product Team,

   I am writing to submit a feature request to address a critical issue we are facing with the management of AWS Root Account email notifications for multiple orgs under our management.

   Issue Summary:
   Currently, when we onboard subsidiaries and assign dedicated AWS Management Account Root email addresses, all notifications are being directed to the same mailbox. This setup results in important notifications being shared across subsidiaries, leading to potential security and privacy concerns. More context on the issue can be found in the related Zendesk ticket: https://doitintl.zendesk.com/agent/tickets/171678

   What is expected :
   We would like a feature that allows us to manage email notifications for each subsidiary independently, ensuring that each organisation receives only the notifications intended for them, without any leakage of information to other subsidiaries.

   Suggested Solutions:
   Implement a way to segregate email notifications at the root level based on the subsidiary.
   Provide a dashboard or tool within the DoIT console that allows for granular control of notification settings for multiple organisations.

   Impact:
   This issue is causing significant concern within our org, as it affects our ability to maintain confidentiality and proper governance across our subsidiaries. It is imperative that we find a solution to manage these notifications effectively and securely.

   Merci :)

   Hello Product Team,

   I am writing to submit a feature request to address a critical issue we are facing with the management of AWS Root Account email notifications for multiple orgs under our management.

   Issue Summary:
   Currently, when we onboard subsidiaries and assign dedicated AWS Management Account Root email addresses, all notifications are being directed to the same mailbox. This setup results in important notifications being shared across subsidiaries, leading to potential security and privacy concerns. More context on the issue can be found in the related Zendesk ticket: https://doitintl.zendesk.com/agent/tickets/171678

   What is expected :
   We would like a feature that… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Discovery  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. A "No Project - General Question" in the drop down when making a ticket?

   Provide a value in the "project" list when users are requesting support that simply says "No project, general question" or "Project N/A"

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Showcase potential Insights savings

   Showcase total potential Insights savings for customers who do not have access to the tool due to their current subscription. This should increase customer visibility and help upsell.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Development  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Enhanced Access to Granular AWS Cost and Usage Data Summary

   Hey la Product Team !

   Summary:
   Customers require access to granular and raw AWS cost and usage data that mirrors the level of detail found in AWS's Cost and Usage Report (CUR).
   The current DoiT console and API provide aggregated data, which lacks some of the required keys present in AWS CUR, such as 'usage start' and 'usage end' dates. Additionally, the inability to fetch the full dataset with a single query
   needs to run multiple requests and merging, which is not ideal and raises concerns about potential performance issues.

   Request details:
   Direct access to raw data: provide a method for customers to directly access the most granular and raw dataset available within DoiT, similar to AWS CUR, without the need for aggregation or data processing that removes essential keys.

   Single query data retrieval: Enable the retrieval of the full dataset in a single query to avoid the need for multiple requests and data merging.

   Dimension and metric selection: Allow customers to select specific dimensions and metrics for download, as per their internal reporting and analytical tool requirements.

   Performance considerations: Ensure that the method for accessing and downloading data is optimised for performance to handle large datasets without significant delays or issues.

   Use Case:
   The feature would be particularly beneficial for customers like Criteo, who have transitioned to being billed by DoiT instead of AWS directly and are implementing FinOps practices that require detailed data analysis.

   Impact:
   This feature would empower customers with precise data for cost management and optimisation, aligning with advanced FinOps practices and internal BI tool integration.

   Merci :)

   Hey la Product Team !

   Summary:
   Customers require access to granular and raw AWS cost and usage data that mirrors the level of detail found in AWS's Cost and Usage Report (CUR).
   The current DoiT console and API provide aggregated data, which lacks some of the required keys present in AWS CUR, such as 'usage start' and 'usage end' dates. Additionally, the inability to fetch the full dataset with a single query
   needs to run multiple requests and merging, which is not ideal and raises concerns about potential performance issues.

   Request details:
   Direct access to raw data: provide a method… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Discovery  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close