Actions
Feature #10914
closed
Include is_private setting in xml/json output
Start date:
Due date:
% Done:
0%
Estimated time:
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
- add
- views/issues/index.api.rsb
- add
api.is_private issue.is_private
- add
Files
Related issues
Updated by Ingo Linde over 13 years ago
+1
Also, can be seen as related to #8577.
Updated by Cory Riddell over 12 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.
Updated by
Updated by Toshi MARUYAMA about 12 years ago
- Related to Feature #8577: "Private" column and filter on the issue list added
Updated by Toshi MARUYAMA about 12 years ago
- Related to Defect #10870: Private bugs are accessible via the API added
Updated by
Updated by Wojciech Brzeziński over 11 years ago
+1
If we have this really simple solution, why it is not included in current realase?
Updated by Wojciech Brzeziński over 11 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.
Updated by Shivam Daryanani about 11 years ago
Uploaded a patch to provide this feature.
Updated by Jean-Philippe Lang about 11 years ago
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Feature added in r13395, thanks.
Updated by Go MAEDA almost 9 years ago
- Has duplicate Feature #16180: Expose Public/Private via API added
Updated by Go MAEDA almost 9 years ago
- Has duplicate Feature #8353: [REST] privacy information on issue displaying added
Actions