Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-8488

Rest API on /rest-service/search-v1 dont have a result

      Issue Summary

      Running the rest api's from the /rest-service/search-v1 does not work as intended and gave empty results.

      Steps to Reproduce

      1. Create review and Jira issue.
      2. Run the following Rest API on both terminal and web browser URL address - /rest-service/search-v1/reviewsForIssue?jiraKey=

      NOTE: All the rest API related to the /rest-service/search-v1 does not work as intended.

      Expected Results

      Output details related to the Jira issue from the Fisheye Crucible reviews.

      Actual Results

      Empty results. Screenshot as attached:

      Details of the review and issue key:

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. FSH_01.png
          FSH_01.png
          13 kB
        2. FSH_02.png
          FSH_02.png
          21 kB
        3. FSH_03.png
          FSH_03.png
          98 kB
        4. FSH_04.png
          FSH_04.png
          108 kB
        5. FSH-05.png
          FSH-05.png
          126 kB
        6. FSH-06.png
          FSH-06.png
          96 kB
        7. FSH-07.png
          FSH-07.png
          144 kB
        8. FSH-08.png
          FSH-08.png
          102 kB

            [CRUC-8488] Rest API on /rest-service/search-v1 dont have a result

            Atlassian Update – 28 February 2023

            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 close 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 Atlassian Bug Fixing Policy for more details.

            If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments and vote on it. We will continue to watch the issue for further updates.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 28 February 2023 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 close 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 Atlassian Bug Fixing Policy for more details. If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments and vote on it. We will continue to watch the issue for further updates. Kind regards Marek Parfianowicz Development Team Lead

            all works fine after linking the Jira issue key in code review

            What if you don't link an issue to the code review (i.e. do not add a link in 'Linked issues' section), but instead of this create a Jira issue out of the comment (by clicking 'Create issue' - they are later shown in the 'Issues raised from comments' section). I'm asking because these are two different link of links (review-issue vs comment-issue).

            Marek Parfianowicz added a comment - all works fine after linking the Jira issue key in code review What if you don't link an issue to the code review (i.e. do not add a link in 'Linked issues' section), but instead of this create a Jira issue out of the comment (by clicking 'Create issue' - they are later shown in the 'Issues raised from comments' section). I'm asking because these are two different link of links (review-issue vs comment-issue).

            Steps to Reproduce. Create review and Jira issue.

            You have to create a new Jira issue from the comment, am I right? Please specify.

            I'm asking, because you can also link a code review to an existing Jira issue (Edit details > Linked issues).

            Actual Results. Empty results.

            Can you confirm that the search finds a Jira issue if it's linked to a code review (Edit details > Linked issues) or when it's mentioned in a summary or objectives fields?

            ... but it cannot find a Jira issue when it's linked to a review comment?

            Marek Parfianowicz added a comment - Steps to Reproduce. Create review and Jira issue. You have to create a new Jira issue from the comment, am I right? Please specify. I'm asking, because you can also link a code review to an existing Jira issue (Edit details > Linked issues). Actual Results. Empty results. Can you confirm that the search finds a Jira issue if it's linked to a code review (Edit details > Linked issues) or when it's mentioned in a summary or objectives fields? ... but it cannot find a Jira issue when it's linked to a review comment?

              Unassigned Unassigned
              bannamalai Baskar Annamalai (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: