Search
Results (12601)
- Defect #6146 (Closed): Subtasks section appearance
- If a user is a manager on a specific project (and not a site administrator), when viewing an issue, the subtasks section does not appear. If th ... trator, the section does appear, as expected.
- Defect #6143 (Closed): Subtask creation form submission race?
- I encountered what seems to be some form of d ... #28907: Test parent":http://demo.redmine.org/issues/28907 ** "#28908: Test child 1":http://demo.redmine.org/issues/28908 ** "#28910: Test child 2":http://demo.redmine.org/issues/28910 ** "#28909: Test child 3":http://demo.redmine.org/issues/28909 (The subtask creation forms were s ... order (1, 2, 3), but as can be seen from the issue numbers, _Test child 3_ happens to have been ... ving their parent field set to the same root issue) * The parent issue sometimes displays only some of the children ... t), or none * Trying to update the affected issues result in server-side Internal errors, or i ... n missing: en, activerecord, errors, models, issue, attributes, parent_issue_id, not_a_valid_parent" error I could onl ... by deleting and recreating all the affected ...
- Defect #6141 (New): No data to display in Documents
- When I sort the documents by author, the mess ... s but can not the authorship of the document.
- Feature #6140 (Closed): REST issues response with issue count limit and offset
- Hi i currently build a Redmine Client Applica ... . I have one Problem. When i request the issues form REST API there is no way to find out how many issues are currently on the Server. On the other ... ke the html one there are variables with the issue count, limit and page number. I write thi ... mes for different pages to find out how many issues i really have. This patch add the attributes issue count, limit and current page to the issues node of the REST API response for issues (issues.xml)
- Defect #6136 (Closed): JSON API holds less information than XML API
- Currently the JSON API provides less informat ... API. Example: http://svn.jdownloader.org/issues/1531.json http://svn.jdownloader.org/issues/1531.xml (1.0.0.stable.3936)
- Defect #6135 (Closed): Default logger configuration grows without bound.
- A naive installation of redmine (following th ... s/11836 which seems to not conflict with the issues in #5706. Consider adding a line to $RED ... to be kind to webappliance installations...
- Feature #6134 (Closed): Issue workflow permissions
- One requirement of our company is that only the issue reporter can close it. The workflow should be: the assignee would set the issue as resolved, then Redmine would automatically assign the issue back to the reporter who can then decide to close or to reassign the issue.
- Defect #6132 (Closed): Allow Key based authentication in the Boards atom feed
- I've looked at the fix in defect 5317 and the code changes are in the appropriate places
- Defect #6131 (Closed): Sort by Group By field does not work
- as above...
- Defect #6130 (Closed): Subtask with 0% sets rollup to 0%
- If you have any subtasks with 0% complete the ... 1 patchlevel 72) * Rails 2.3.5 * 1.0.0-RC
- Defect #6128 (Closed): "assigned_to" seem to be ignored when creating issues via REST API
- sending request: <pre> POST http://172.17.10.53:3000/issues.xml HTTP/1.1 -> <issue><project_id>ace</project_id><subject>test zz ... assigned_to name="Alexey Skor" id="19640"/></issue> </pre> response: <pre> HTTP/1.1 201 Created </pre> but the new issue's "assignee" is empty. I verified there's a user with such id. I'm trying to use the same <issue> format as I see in the response from Redmine when I retrieve issues list. is this REST API's limitation that assignee can't be set on issue creation or I should use different format fo ... there's a documentation somewhere about that.
- Feature #6127 (Closed): Preceeded by / followed by - Same day
- The current validation for issues that are linked by preceeded by / followed by issue links is that the start date of the latter c ... former. For example this is not possible (Issue B follows Issue A) Issue A - 2010/01/01 to 2010/01/10 Issue B - 2010/01/10 to 2010/01/20 The following issue must always start on the next day. This s ... day as the last day of the preceding task.
- Defect #6126 (Closed): "project id" node is ignored when creating issues via REST API
- this is the XML body I'm sending from my program to Redmine (last trunk version): <pre> <issue><project_id>ace</project_id><parent id="46"/><subject>child 1</subject></issue> </pre> POST http://172.17.10.53:3000/issues.xml HTTP/1.1 ----------------------------- ... 03 <?xml version="1.0" encoding="UTF-8"?> <issue> <id>51</id> <project name="ace" id="7 ... pdated_on> <relations> </relations> </issue> </pre> my output: <pre> created child: issue: id=51 assignee: subject:child 1 </pre> I have the issue with id "46" in the same "ace" project so I expect the new issue to be created with the parent link, but it's ... here's Redmine log: <pre> Processing ...
- Feature #6125 (Closed): search finds attached files by name and content
- Dear Redmine people, perhaps this has been su ... ould be even better if the search could find issues by the name (and even content) of attached documents. Often, issues are created with fairly generic names or the focus of an issue changes with time. Defining information for the issue may be an uploaded use case or document not the comments in the issue. HTH and thanks for a great product craig
- Feature #6122 (New): Adding subtasks to "real" task (not "container" task)
- Imagine situation: I am working on feature ... racking, Due date, % done and other features.
- Feature #6121 (Closed): Reports Summary page displays only issues of a project not of all its subprojects
- I'm using 1.0 stable checkout from http://red ... d Administration option "Display subprojects issues on main projects by default" so on parent project issues lists also issues from subprojects are displayed The Reports Summary page currently displays only issues from the currently selected project and not (as I would expect) issues from all containing subprojects. I think ... Thanks and keep up the great work :)
- Feature #6119 (New): Double "Group by" in issue-list filter options
- I would like to have a option on the issue's filter to group by two columns instead of ... y year and month in due date. Thank you. Petr
- Feature #6118 (Closed): Filter by parent task or subtasks
- There doesn't seem to be an option to use "pa ... Task is null" - so that I get all top-level issues (as well as issues without any children).
- Feature #6117 (New): subtasks default to parent issue target version
- I have been asked if it is possible to have s ... e target version as the parent when the "new issue" screen is opened or the parent ID is assigned.
- Feature #6116 (New): Group sub-tasks with parent on issue list
- My colleagues have starting re-arranging their issue lists now that we have subtasks and every single one of them has asked how they can change the issue listing to make it obvious at a glance which subtasks belong to which issue. Having this ability is a critical featur ... all subtasks under their parent tasks in the issue listing. add a - or > in the issue title as basic indentation. I imagine thi ... fect how the table ordering code should work.
- Feature #6115 (Closed): Parent issue id field in issue bulk edit.
- It would be very useful to be able to assign ... ve many people who have to re-organise their issues now that we have sub-tasks.
- Defect #6114 (Closed): Empy repository screen
- I recently switch Redmine from one server to ... t the records were gone and the links on the issue pages are no longer present. I then reloc ... ds are in the DB and the links appear on the issues page. If I click a commit link from an issue then I go to the correct repository page for ... iew page with no parameters that fails.
- Feature #6112 (Closed): Accept localized keywords when receiving emails
- Redmine should allow me to send and e-mail us ... instead of "Attributed to:" to attribute an issue to some user. pt-BR and en respectively. This should work for every keyword in MailHandler.
- Feature #6111 (Closed): Issue bulk edit should provide "NONE" option for List custom field
- When I make a bulk edit for issues, the <select> for a List custom field should have a "none" option.
- Defect #6110 (Closed): MailHandler should allow updating Issue Priority and Custom fields
- @MailHandler#receive_issue_reply@ does not update issue priority and custom fields. Those attributes can be given in the mail body if an issue is created (as this uses @MailHandler#receive_issue@) but not on update.