Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-7351

Slash character is not supported in REST API URLs

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      When using FeCru REST APIs, if the name of the object, such as permission scheme, contains a slash character ( / ), then the call will fail with 404, even if the slash is replaced with its URL encoded character(s).

      The suggestion here is to either:

      • support slash (or its URL encoded character) in the REST API
      • add support for object IDs, rather than names, in the REST API
      • ensure an object cannot be created with a slash in its name

      The last option is based off current workaround of renaming the object without the slash in the name.

            [FE-7351] Slash character is not supported in REST API URLs

            Marek Parfianowicz added a comment -
            Atlassian Update – 8 July 2024

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed 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. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. 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.

            Kind regards
            Marek Parfianowicz
            Principal Engineer

            Marek Parfianowicz added a comment - Atlassian Update – 8 July 2024 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed 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. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. 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. Kind regards Marek Parfianowicz Principal Engineer

              Unassigned Unassigned
              kplaha Kanwar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: