Feature #10914

Include is_private setting in xml/json output

Added by Cory Riddell almost 6 years ago. Updated over 3 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:REST API
Target version:2.6.0
Resolution:Fixed

Description

When getting issues with the REST api, the is_private flag isn't included.

I've solved the problem on my local copy by modifying two files:

  • views/issues/show.api.rsb
    • add
      api.is_private @issue.is_private
  • views/issues/index.api.rsb
    • add
      api.is_private issue.is_private

Adds-issue-is_private-to-api.diff Magnifier - Git patch series (2.43 KB) Shivam Daryanani, 2014-08-20 21:04


Related issues

Related to Redmine - Feature #8577: "Private" column and filter on the issue list Closed 2011-06-09
Related to Redmine - Defect #10870: Private bugs are accessible via the API Closed
Duplicated by Redmine - Feature #16180: Expose Public/Private via API Closed
Duplicated by Redmine - Feature #8353: [REST] privacy information on issue displaying Closed 2011-05-12

Associated revisions

Revision 13395
Added by Jean-Philippe Lang over 3 years ago

Issue API: include is_private attribute in xml/json output (#10914).

Patch by Shivam Daryanani.

History

#1 Updated by Ingo Linde almost 6 years ago

+1

Also, can be seen as related to #8577.

#2 Updated by Cory Riddell about 5 years ago

#8577 fixes the issue for the issue list, but does not address the problem with including the is_private flag in the json / xml output.

#3 Updated by d okumura over 4 years ago

+1
Seems to relate with #10870

#4 Updated by Toshi MARUYAMA over 4 years ago

  • Related to Feature #8577: "Private" column and filter on the issue list added

#5 Updated by Toshi MARUYAMA over 4 years ago

  • Related to Defect #10870: Private bugs are accessible via the API added

#6 Updated by Benoit Duffez about 4 years ago

+1

#7 Updated by Wojciech Brzeziński almost 4 years ago

+1
If we have this really simple solution, why it is not included in current realase?

#8 Updated by Wojciech Brzeziński almost 4 years ago

I would also suggest change this issue track to 'Bug', 'Defect' or something similar, because we can modify this field with PUT request. All Issues obtained with REST api seems to be not private now.

#9 Updated by Jean-Philippe Lang almost 4 years ago

  • Target version set to 2.6.0

#10 Updated by Shivam Daryanani over 3 years ago

Uploaded a patch to provide this feature.

#11 Updated by Jean-Philippe Lang over 3 years ago

  • Status changed from New to Closed
  • Assignee set to Jean-Philippe Lang
  • Resolution set to Fixed

Feature added in r13395, thanks.

#12 Updated by Go MAEDA over 1 year ago

#13 Updated by Go MAEDA over 1 year ago

  • Duplicated by Feature #8353: [REST] privacy information on issue displaying added

Also available in: Atom PDF