• 0
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Hi, It would be super helpful to incorporate a warranty check pattern in ID. It's already being done by the asset management tool Device42 which retrieves device warranty info directly from manufactures like Dell, HP, Lenovo and IBM. This would be incredibly helpful in managing the life cycle of our assets.https://docs.device42.com/auto-discovery/warranty-autodiscovery/

          Form Name

            [JSDSERVER-7662] Retreive Device Warranty Info via API

            Atlassian Update – 20 November 2023

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. Because of the fact that Assets Discovery product is highly customizable via custom patterns, we encourage our customers to create their own patterns to cover specific use-cases.

            The feature requested is very low on our priority list, and will not be implemented in the foreseeable future. That's why we've decided to resolve it as Not being considered.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Marek Parfianowicz added a comment - Atlassian Update – 20 November 2023 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. Because of the fact that Assets Discovery product is highly customizable via custom patterns, we encourage our customers to create their own patterns to cover specific use-cases. The feature requested is very low on our priority list, and will not be implemented in the foreseeable future. That's why we've decided to resolve it as Not being considered . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

              Unassigned Unassigned
              da0dd4439f59 Alex Cooksey
              Votes:
              11 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: