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

Add current comment resolution status to REST

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Integrations
    • 1
    • 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.

    Description

      REST endpoints:

      1. /rest-service/reviews-v1/{id}/comments
      2. /rest-service/reviews-v1/{id}/comments/general
      3. /rest-service/reviews-v1/{id}/comments/versioned
      4. /rest-service/reviews-v1/{id}/comments/{cId}
      5. /rest-service/reviews-v1/{id}/comments/{cId}/replies
      6. /rest-service/reviews-v1/{id}/reviewitems/{riId}/comments

      need to get current resolution status (needs resolution (by whom) / resolved (by whom)). Probably 1 change will fix all of the endpoints listed above.

      Getting full history (if implemented at all) needs a separate end point.

      Note the data is already exposed in Java API, see https://docs.atlassian.com/fisheye-crucible/latest/javadoc/com/atlassian/crucible/spi/services/ReviewService.html#getCommentResolution-com.atlassian.crucible.spi.PermId-

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              kcichy Kamil Cichy
              Votes:
              16 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated: