Activity
From 2016-05-04 to 2016-05-06
2016-05-06
-
21:06 Feature #22676 (Closed): Static issue list URLs
- Done, see #4806.
You can use the context menu on the issue list to link to a query that filters the selected issues, or generate a link manually, eg: @/issues?issue_id=17302,17322&set_filter=1&status_id=*@ -
21:02 Feature #4806 (Closed): Filter the issue list by issue ids
- Feature added. You can filter on one or multiple (using comma separated ids) issue ids, or by range.
-
18:57 Defect #22754: Error while updating issues with boolean custom field through API
- Did problem begin when you upgrading Redmine?
Christopher Gabriel wrote:
> we are running 2.2.4.stable where the problem is raised.
version:2.2.4 is not maintained.
-
18:37 Defect #22754: Error while updating issues with boolean custom field through API
- I can't do that unfortunately, but I couldn't find reference to this issues in recent version's changelogs. we are running 2.2.4.stable where the problem is raised.
-
18:35 Defect #22754: Error while updating issues with boolean custom field through API
- Did you upgrade Redmine?
-
16:20 Defect #22754: Error while updating issues with boolean custom field through API
- More updates:
the custom field 207
"custom_fields"=>[{"id"=>207, "value"=>1}]
is a boolean field. Sending the value of 1 (integer), will lead to the given error 500. Using "1" (string) as value, will work fine. -
15:01 Defect #22754 (Closed): Error while updating issues with boolean custom field through API
- We started having trouble while updating an issue through the API. Some client code worked fine for almost 2 years.
Hints? -
18:56 Patch #22756 (Closed): Edit versions links on the roadmap
-
17:46 Defect #22733 (Closed): 404 The entry or revision was not found in the repository
- Sw Dev wrote:
> Do you believe the repository setup is dependent on the server environment? If yes, it would be good to explain in the documentation which part of the repository setup is platform dependent and which not. The documentati... -
15:16 Defect #22733 (Reopened): 404 The entry or revision was not found in the repository
- OK, I have asked a question in the forums.
Please excuse for reopening but it seems important to add these comments:
May I suggest an improvement of the error message in this situation? "404 The entry or revision was not found in ... -
12:38 Feature #22752 (Closed): Draft feature
- Similar to email a draft feature can be enabled. So we can save the information before entering the defect.
-
12:02 Feature #22434: Block user via API
- You can set the status of the user using a [[Rest_Users#PUT|PUT request]]. There, you can set the status as follows (here using json):
2016-05-05
-
21:35 Defect #22745 (Closed): Rest API for Custom Fields does not return keys for key/value types
- When using the REST API to retrieve the list of custom_fields by calling http://localhost:3000/custom_fields.json , if there is a Key/Value list type custom fields only the value comes back, as in the example below:
-
18:13 Defect #21037 (New): Issue show : bullet points not aligned if sub-task is in a different project
-
15:51 Defect #22740 (Closed): Redmine is not working
- Please use forum for question.
-
13:50 Defect #22740: Redmine is not working
- This is on Windows 7 and Redmine Apache, MySQL and Subversion services are running. THin 1 and Thin 2are down.
-
13:49 Defect #22740 (Closed): Redmine is not working
HI All,
Redmine stops working suddenly after server reboot.
[Thu May 05 17:11:31.585990 2016] [proxy:error] [pid 6648:tid 1272] (OS 10061)No connection could be made because the target machine actively refused it. : AH00957:...-
13:58 Feature #8241: Advanced notification: per user, per project configurable schedule, event filter and notification format
- +1
-
10:33 Defect #22733 (Closed): 404 The entry or revision was not found in the repository
- Please use forum for question or ask bitnami team.
-
09:50 Defect #22733 (Closed): 404 The entry or revision was not found in the repository
- Environment: Redmine 3.2.1 with Bitnami Virtual Machine.
Goal: setup a Git repository.
This might have been resolved but none of the solutions worked in my setup. I followed these instructions: https://www.redmine.org/projects/redmin... -
05:44 Patch #22732 (Closed): Traditional Chinese translation (to r15362)
- * New:
** label_wiki_page_new, label_relations: Relations
2016-05-04
-
15:09 Patch #22724 (Closed): Change Japanese translation for "last name" and "first name"
- I suggest changing Japanese translation for "last name" and "first name", from "苗字" and "名前" to "姓" and "名".
* "名前" is ambiguous. It can be interpreted either as "first name" or "full name" in Japanese.
* "姓" and "名" is more generic ... -
14:43 Defect #13654: Can't set parent issue when issue relations among child issues are present
- Thomas Koch wrote:
> The Problem still exists with Redmine 3.2.0.stable.
The target revision appears to be 3.3.0. -
14:37 Defect #13654: Can't set parent issue when issue relations among child issues are present
- The Problem still exists with Redmine 3.2.0.stable.