Activity
From 2010-08-12 to 2010-08-14
2010-08-14
-
14:43 Defect #5964 (Resolved): Error 500 when adding a subtask
- Yes, it does now return 0. And, today, I do not get any 500 error, so I think all of this is now solved and unreproducible. It is now running perfectly well, except some style issues inside our unified layout.
Thank you so much! -
05:17 Defect #5964: Error 500 when adding a subtask
- OK. Now retry @Issue.count(:conditions => {:rgt => nil})@, you should get "0". The method that used to bring you problems now works. So if you get 500 errors now, I guess they are not the same as before.
I strongly encourage you to po... -
10:05 Defect #6132: Allow Key based authentication in the Boards atom feed
- Hello, this happens to me too. However, I am using Safari and try to view
feed://myserver/redmine/activity.atom?key=xxxx
And it returns 0 items. -
09:55 Feature #1460: Project Plan import/export utility
- Xabier,
I think I am in love with Ruby right now... it was as straight forward as possible.
I am reposting my pt-BR.yml translation, because I have realized I had made a stupid mistake (my bad), and I would like you to consider app... -
08:21 Feature #1460: Project Plan import/export utility
- And it won't run with Redmine 1.0.0.devel.3940 - beware of upgrades - I had to roll back.
-
07:52 Feature #1460: Project Plan import/export utility
- Xabier Elkano wrote:
> Fabio Leitao wrote:
> ...
I am still a _ruby_ newbie, but I'm looking forward for the chalenge, I'll try to understand it better, make my changes and experiment for a while... I hope I can figure out where to adj... -
06:14 Defect #6126: "project id" node is ignored when creating issues via REST API
- btw, just noticed that I made a mistake in "subject" field: should be "parent id" instead of "project_id"
-
06:10 Defect #6126: "project id" node is ignored when creating issues via REST API
- this works, thanks.
see my comment for task #6128 : http://www.redmine.org/issues/6128#note-2 -
05:49 Defect #6128: "assigned_to" seem to be ignored when creating issues via REST API
- thanks, this works.
XML response for "get issues" and "get issue" requests has different structure, that's why I expected that parameter to be in -
01:06 Defect #6130: Subtask with 0% sets rollup to 0%
- I'm not able to reproduce this issue on the Redmine demo site.
See e.g. http://demo.redmine.org/projects/issue6121-2-1/issues?query_id=509. Here you can see that issue 28762 has two subtasks (28763 and 28846) with each a different @%-...
2010-08-13
-
21:46 Defect #5964: Error 500 when adding a subtask
- OK, I tried with a freshly downloaded Redmine 1.0.0, with copied database.yml and email.yml, not any other file.
-
09:57 Defect #5964: Error 500 when adding a subtask
- Just one more thing : when you'll have files in 1.0.0 version and db:migrate run correctly, @Issue.rebuild!@ may not be sufficient. If problems persists after you ran @Issue.rebuild!@ and it returned "true", you can try @Issue.update_all...
-
09:32 Defect #5964: Error 500 when adding a subtask
- Thibaut Cuvelier wrote:
> > Your 2 errors seem to occur when calling Issue#leaf? method, which is part of awesome_nested_set plugin. Can you confirm this in a console :
> ...
It's part of redmine core, it's not a plugin a user have to... -
20:20 Feature #3967: Ability to define default columns to display based on project
- +1 for this feature. This seems like something that should be a core feature. I will give Vitaly's plugin a try.
-
18:53 Feature #5864: Regex Text on Receiver Email
- +1
-
18:41 Feature #6140: REST issues response with issue count limit and offset
- now on github
http://github.com/danlin/redmine/commit/f8d2d207d1c60628eb4fdb10402af6eba5dfbe60 -
16:18 Feature #6140 (Closed): REST issues response with issue count limit and offset
- Hi i currently build a Redmine Client Application for some Mobile Devices.
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 responses l... -
17:51 Feature #1086: Fine grained permissions
+1.
-
17:34 Defect #6132: Allow Key based authentication in the Boards atom feed
- Well, you seem to have the right codebase, so I'm a little at a loss here…
Could you have a look at the redmine log (probably in @redmine_dir/log/production.log@), hit the atom link with wget or curl and paste the error here? -
14:45 Defect #6132: Allow Key based authentication in the Boards atom feed
- Hello.
I got the release from BitNami (http://bitnami.org/). In the root folder changelog.txt has as it's latest entry
Version 1.0.0-0 2010-07-22
*Update Remdine to 1.0.0
The Remdine is a spelling mistake in the changelog.tx... -
14:38 Defect #6132: Allow Key based authentication in the Boards atom feed
- Are you sure you have 1.0 or at least that your upgrade went through if you upgraded recently? All ATOM links I could find (the ones for automatic discovery included) are of the form @http://host/projects/identifier/boards/id.atom?key=XX...
-
14:13 Defect #6132: Allow Key based authentication in the Boards atom feed
- Also if you use Feed Validator is complains
http://www.feedvalidator.org/check.cgi?url=http%3A%2F%2F80.177.48.68%2Fredmine%2Fprojects%2Frmfbc%2Fboards%3Fformat%3Datom%26key%3D8361485aeaa58a50f8a57a76f0935e84e07f1f84 -
14:11 Defect #6132: Allow Key based authentication in the Boards atom feed
- Hello - thanks for the response. BTW - I think Redmine is brilliant.
I've made no code changes.
The url is http://80.177.48.68/redmine/projects/rmfbc/boards?format=atom&key=8361485aeaa58a50f8a57a76f0935e84e07f1f84
If you put th... -
13:46 Defect #6132: Allow Key based authentication in the Boards atom feed
- Mmh, that works for me:
-
11:53 Defect #6132: Allow Key based authentication in the Boards atom feed
- Sorry. It's not a feed from the project, it's a feed from the Forums associated with the project. So if I create a project, then a forum for that project and add a post in the forum then try and access the Atom feed externally I get a 50...
-
11:48 Defect #6132: Allow Key based authentication in the Boards atom feed
- If you are on 1.0 you don't need any patches.
Please see [[SubmittingBugs]], especially: What ATOM feed exactly? Does it produce an error in the log? -
11:44 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
-
17:10 Defect #6139 (Closed): teste
- Please use the "demo redmine":http://demo.redmine.org for testing.
-
16:08 Defect #6139 (Closed): teste
- tarefa com finalidade de testar!!
-
17:05 Defect #6135: Default logger configuration grows without bound.
- T. Hauptman wrote:
> Personally I think that defaulting a configuration that is sane, even if it's nerf, is better in the long run. Power admins can always tweak it to match their optimized system. The rest of us want to install as quic... -
16:26 Defect #6135 (Resolved): Default logger configuration grows without bound.
- Personally I think that defaulting a configuration that is sane, even if it's nerf, is better in the long run. Power admins can always tweak it to match their optimized system. The rest of us want to install as quickly as possible with t...
-
14:18 Defect #6135: Default logger configuration grows without bound.
- Mmh, I thought the docs had been updated to reflect that… IIRC the rationale for not including what you propose is that we don't want to impose any rotation scheme on anyone, everyone potentially having different requirements. The other ...
-
13:55 Defect #6135 (Closed): Default logger configuration grows without bound.
- A naive installation of redmine (following the install instructions) leaves logfiles in an unexpected place, growing without limit. This can cause problems for the system admin.
A solution was proposed in Defect #5706 but not accepted... -
15:15 Defect #6138 (Closed): Тест системы
- Please use the "demo redmine":http://demo.redmine.org for testing.
-
15:05 Defect #6138 (Closed): Тест системы
-
15:14 Defect #6137 (Closed): CPU that does not work
- I think you've hit the wrong redmine, sorry.
-
14:57 Defect #6137 (Closed): CPU that does not work
- Please remove CPU from my room that has not worked since the 2008 school year.
-
14:55 Defect #6131: Sort by Group By field does not work
- OH: I just discovered you can "GROUP BY blah ASC" in at least sqlite and mysql. Needs to be tested, but we may have a clean workaround if it's supported on each of our databases and/or by rails adapters.
-
14:51 Defect #6131: Sort by Group By field does not work
- Do you think we should / could find a workaround ?
-
14:32 Defect #6131: Sort by Group By field does not work
- Ah, I think I know what's happening :-)
The "group by" and "sort by" don't influence each other. If you remove the "group by", the issues will be sorted correctly/as expected, if you specify a "group by", the issues inside the groups ... -
14:22 Defect #6131: Sort by Group By field does not work
- In the screenshot, the groups are not sorted like expected (from a user point of view I mean, this may be a "standard" SQL behavior, I'm not sure). Group 1.1.0 is displayed before group 1.0.1, whereas Michalis asked for a sort by target ...
-
13:51 Defect #6131: Sort by Group By field does not work
- AFAIK versions are sorted by due date first, and names after that. Still no bug that I can see.
-
13:06 Defect #6131: Sort by Group By field does not work
- As if the sorting is made on some internal key?
-
13:04 Defect #6131 (Reopened): Sort by Group By field does not work
- Sorry, the following scenario in this site reproduces it:
the following query:
!Query.gif!
produces this result:
!Result.gif! -
11:45 Defect #6131 (Closed): Sort by Group By field does not work
- Can't reproduce.
See [[SubmittingBugs]]. -
09:18 Defect #6131 (Closed): Sort by Group By field does not work
- as above...
-
14:25 Defect #6136 (Closed): JSON API holds less information than XML API
- Currently the JSON API provides less information than the XML API. E.g. custom fields (resolution) isn't accessible by the JSON API.
Example:
http://svn.jdownloader.org/issues/1531.json
http://svn.jdownloader.org/issues/1531.xml
... -
12:36 Defect #6114: Empy repository screen
- I did have it before so that the repo directories were owned by the redmine user (member of the apache group) that owned the redmine web-app files but that didn't work either IIRC.
Cannot check until Monday now; will double check when... -
11:35 Defect #6114: Empy repository screen
- Passenger apps do not necessarily run as the same user as apache, check the passenger docs for more info (you could inspect the process list to find out what user redmine is run as).
-
06:36 Defect #6114: Empy repository screen
- Maybe the git shell output will help?
git version 1.7.2 (Latest stable) -
06:34 Defect #6114: Empy repository screen
- changed log level to debug, the
-
06:27 Defect #6114: Empy repository screen
- production.log file if it is of any use.
-
06:23 Defect #6114: Empy repository screen
- Did some checking:
I cannot see the repository main page
I cannot see the contents of a file
I cannot see the diff of a file
The repositories are stored in /var/repositories
/var/repositories and all sub-folders / files are ow... -
12:19 Feature #5541: Project Status "Closed"
- +1
-
12:17 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 de... -
11:53 Feature #6133 (Closed): galeria
- Please use the "demo redmine":http://demo.redmine.org for testing.
-
11:46 Feature #6133 (Closed): galeria
- galeria do spicy
-
11:43 Defect #6129 (Closed): test
- Please use the "demo redmine":http://demo.redmine.org for testing.
-
08:09 Defect #6129 (Closed): test
- test
-
11:39 Defect #6126: "project id" node is ignored when creating issues via REST API
- @<parent_issue_id>46</parent_issue_id>@
-
01:44 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):
-
11:37 Defect #6128: "assigned_to" seem to be ignored when creating issues via REST API
- Try @<assigned_to_id>USERID</assigned_to_id>@ in the @<issue></issue>@ block.
-
05:12 Defect #6128 (Closed): "assigned_to" seem to be ignored when creating issues via REST API
- sending request:
-
11:32 Feature #5997: REST API should provide valid xml response with status for EVERY request
- Alexey Skor wrote:
> - does ":X@" stand for some value I need to put or it must be exactly ":X@" in the url (which didn't work for me)?
It can be whatever value you want, IIRC you can give the key as username and anything as password... -
06:50 Feature #5997: REST API should provide valid xml response with status for EVERY request
- thanks a lot.
a question: in this sample URL -
01:37 Feature #5997: REST API should provide valid xml response with status for EVERY request
- Alexey Skor wrote:
> I'm still stuck with this "POST" request for issues creation. Does anyone has an example of valid HTTP POST request for this? I don't need Java code, just a request body itself is fine.
One with username and pass... -
10:16 Feature #1460: Project Plan import/export utility
- Fabio Leitao wrote:
> Almost forgot to ask... the tasks that already had some % of progress (but not yet 100%) got imported on "feedback" mode, while the uninitiated ones got the project folder as "new"
> ...
I am very novice in ruby... -
03:07 Feature #1460: Project Plan import/export utility
- Almost forgot to ask... the tasks that already had some % of progress (but not yet 100%) got imported on "feedback" mode, while the uninitiated ones got the project folder as "new"
Is this the expected behaviour? Would it be difficult... -
02:46 Feature #1460: Project Plan import/export utility
- Xabier Elkano wrote:
>
> ...
Xabier,
:D It worked like a charm! Already importing tasks and milestones from OpenProj XML files... I'll try MS Project this weekend (don't have any now).
By the way, here is my pt-BR.yml translatio... -
09:58 Defect #5608: broken with i18n 0.4.0
- Martin Frost wrote:
> It might be that if they were to use @#{}@, then people would believe they could input arbitrary ruby code, and they want to make a distinction from that. This is just a wild guess on my part though.
Sounds like... -
09:42 Defect #5608: broken with i18n 0.4.0
- Jean-Baptiste Barth wrote:
> Eric Davis wrote:
> ...
It might be that if they were to use @#{}@, then people would believe they could input arbitrary ruby code, and they want to make a distinction from that. This is just a wild guess o... -
09:24 Defect #5608: broken with i18n 0.4.0
- Eric Davis wrote:
> That's cute. Anyone up for writing a script to update all of the locale files?
I can. Do you want it before 1.0.1 ? It may be a bit risky to change the gem version 7 days before release...
Anyway, I wonder why... -
01:46 Defect #5608: broken with i18n 0.4.0
- Martin Frost wrote:
> 0.4.1 has deprecated the {{key}} syntax as well. The new syntax is %{key}, so those changes will have to be made to all locale files.
That's cute. Anyone up for writing a script to update all of the locale files? -
08:18 Defect #6130 (Closed): Subtask with 0% sets rollup to 0%
- If you have any subtasks with 0% complete the parent task will be set to 0% regardless of the percent complete of the other subtasks.
* MySQL 5.0.90-community-nt
* Ruby 1.8.7 (2008-08-11 patchlevel 72)
* Rails 2.3.5
* 1.0.0-RC
-
08:08 Defect #6045 (Resolved): Repository file Diff view sometimes shows more than selected file
- It was just missing path information, fixed in r3939
-
07:38 Defect #6045: Repository file Diff view sometimes shows more than selected file
- I don't really like the idea of using request.request_uri, it could introduce weird bugs, but I'll take a look at this one. I confirm it could be the kind of defect we want to address in 1.0.1, but I don't know when Eric wants to stop ad...
-
05:21 Defect #6045: Repository file Diff view sometimes shows more than selected file
- @ Marc: Thanks for your contribution. Sadly the patch-file seems to be broken somehow but nevertheless I have extracted the change locally...
It includes a one-line change of source:/trunk/app/views/repositories/diff.rhtml@3938#L4
... -
08:02 Feature #2069: Wiki syntax to link to files in the files-module
- +1. We currently need to paste full URLs to the object to get this functionality, but it would reduce maintenance quite a bit if one could link directly to objects in the files module.
-
06:34 Feature #6119: Double "Group by" in issue-list filter options
- Improved the issue-properties to make it easier to find.
-
06:27 Feature #643: Issue description templates
- This is indeed related to patch #2931, which is related also to issue #1138 which itself seemed to be a duplicate of this issue. I've closed #1138 in favor of this older issue.
I've also modified this issues properties subject and categ... -
06:23 Feature #1138 (Closed): Issue templates
- Closed in favor of duplicated issue #643.
-
06:17 Feature #6115 (Closed): Parent issue id field in issue bulk edit.
- Closed as a duplicate of issue #5831.
-
06:11 Feature #6121: Reports Summary page displays only issues of a project not of all its subprojects
- Basic (as in issues open/closed or in other issue-statuses) information about the issues in the parents child projects *are* included in the report under the "Subproject"-section. See e.g. this "demo project report":http://demo.redmine.o...
-
05:36 Defect #6123: help/wiki_syntax_detailed.html is outdated
- I'll do a rewrite of those[1] pages upcoming weekend so it can be included in Redmine version#21.
Thanks for the notification.
fn1. this includes two pages:
* source:/trunk/public/help/wiki_syntax.html@3938
* source:/trunk/public... -
05:26 Defect #5721 (Resolved): attachment filename Chinese garbled in using receiving mail to create issue
-
05:08 Patch #2931: Templating for description of new tickets by Tracker
- Light Kong, the description is changed only on creation of an issue (new record) in order to prevent the lost of issue's description when editing. Feel free to change this behavior.
-
04:35 Feature #6127 (Closed): Preceeded by / followed by - Same day
- Closed as a duplicate of issue #5655 (which also includes a hack for the thing).
-
03:26 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 cannot be the same as the finish date of the former.
For example this is not possible (Issue B follows Is... -
03:04 Feature #4786: Gantt Chart - Grouping issues by target version
- The grouping by sub-tasks is working nicely with the new sub-task core feature. I havent had a chance to see how sub-projects and sub-tasks mix. Will have to look into that.
-
02:21 Feature #6116: Group sub-tasks with parent on issue list
- Aha, that is perfect, just what I want. Apart from the fact that we have to have the parent task column visible which takes up a lot of space we would rather use for other stuff.
A way to get this exact layout without having to have t... -
01:34 Feature #6125 (Closed): search finds attached files by name and content
- Dear Redmine people, perhaps this has been suggested before but I think the package would 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... -
00:28 Feature #401: Add pdf export for WIKI page
- You could maybe make use of "Apache FOP":http://xmlgraphics.apache.org/fop/
2010-08-12
-
20:26 Feature #6122: Adding subtasks to "real" task (not "container" task)
- Jan Nowak wrote:
> But if I add A.1, A.2... as subtasks of A, I lose Time tracking, Due date, % done and other features.
Ok, so don't do that. Move A into a more global issue for instance. The actual feature is actually here to compu... -
13:25 Feature #6122: Adding subtasks to "real" task (not "container" task)
- So for example,
Total Hours of task should be Sum of all subtasks total hours PLUS task's own total hours -
13:20 Feature #6122 (New): Adding subtasks to "real" task (not "container" task)
- Imagine situation:
I am working on feature A. I am doing it several days, updating %Done, filling time log, writing comments, uploading files and so on. I finish it. But now I see several other features/bugs that are based on feature ... -
19:50 Defect #5964: Error 500 when adding a subtask
- > Your 2 errors seem to occur when calling Issue#leaf? method, which is part of awesome_nested_set plugin. Can you confirm this in a console :
Well ... this plugin has never been installed ...
However, I get stoned by Ruby when tr... -
19:49 Defect #6045: Repository file Diff view sometimes shows more than selected file
- Here's a patch for it...
-
18:31 Defect #6045: Repository file Diff view sometimes shows more than selected file
- Just to be more specific, this is due to the wrong URI in the action= of the <form> around the inline/side-by-side selection. It is missing the file pathname part.
-
18:46 Feature #6124 (New): REST get report
- Hi, It's a idea through REST get reports, including custom fields.
With this, I can create custom report.
Thank
Rodrigo -
17:54 Defect #6114: Empy repository screen
- Transposed the numbers; meant to say #5628.
Will double check permissions. -
16:17 Defect #6114: Empy repository screen
- Jeffrey Jones wrote:
> Possibly related to #5268?
What could an error on the repository page possibly have to do with some OpenID stuff?
Anyway, make sure your permissions are correct, I would suppose you see revisions because the... -
03:43 Defect #6114: Empy repository screen
- Possibly related to #5268?
-
03:41 Defect #6114 (Closed): Empy repository screen
- I recently switch Redmine from one server to another and updated it to 1.0.0-RC. This also involved moving the git repositories around.
One the new server I deleted the repository from the project in Redmine and verified in the DB tha... -
17:02 Feature #6092: Truncate Git revision labels in Activity page/feed and allow configurable length
- Agreed Felix. I'll work on moving it at least into a variable if not into a setting. Also, sorry about changing the ticket status, I'll know now not to do that anymore.
-
09:35 Feature #6092 (New): Truncate Git revision labels in Activity page/feed and allow configurable length
- Please leave the status changes to the devs, thank you. (resolved is for patches in trunk but not in stable yet).
The patch looks good to me, I'm not sure we'd need it configurable either. If we take the git etiquette of 72 chars per ... -
07:32 Feature #6092: Truncate Git revision labels in Activity page/feed and allow configurable length
- Oh, I should mention I didn't implement this as a configurable setting as requested. Maybe later...
-
07:30 Feature #6092 (Resolved): Truncate Git revision labels in Activity page/feed and allow configurable length
- Attached patch applies the fix. Also available at http://github.com/asoltys/redmine
-
14:47 Defect #6089: Large uploads fails with Firefox
- The problem is the same with Firefox on a Linux box.
I found this thread: http://www.webmasterworld.com/forum88/13149.htm where a connection
with -
14:02 Feature #703: Configurable required fields per tracker/status/role
- Think would be nice to be able to do a "fine tuning" on view/change field permissions for roles. And also have a "default permissions settings" feature in the scope of the category, project and overall.
This comment also (or better) a... -
14:00 Defect #6123 (Closed): help/wiki_syntax_detailed.html is outdated
- help/wiki_syntax_detailed.html in current trunk is not identical to: http://www.redmine.org/wiki/1/RedmineTextFormatting
Specifically, it does not mention sections of ordered/unordered lists and tables. -
13:51 Feature #1460: Project Plan import/export utility
- Fabio Leitao wrote:
> Simon,
> ...
Fabio, I've just modified the plugin to support other languages. I've also modified some code to support openproj and ganttproject, because we work with them.
My plugin version is a bit different bec... -
09:45 Feature #1460: Project Plan import/export utility
- Simon,
I have been reading the code from your plugin and I have to thank you a lot for your effort.
I was trying to collaborate but I could translate to my own language (pt-BR) without messing with the actual code since there is no... -
13:46 Feature #5084: Filter all isssues by projects
- I just installed the revision and it works great. Thank you for your help.
-
00:01 Feature #5084: Filter all isssues by projects
- Jean-Baptiste Barth wrote:
> Added project filter in r3927
This has also solved the request of (duplicated) feature request #1963. Updated and related that one according to this issue.
@JBB: Thanks for fixing this issue... :) -
11:32 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://redmine.rubyforge.org/svn/branches/1.0-stable revision 3902 on windows machine
I have enabled Administration option "Display subprojects issues on main projects by default" so on parent projec... -
10:29 Feature #6120 (Closed): keep autologin cookie with several web browsers
- With the revision r2778, only one autologin cookie is kept.
You should keep the tokens table clean or for the security, but it's a problem when you use several web browsers or computers, you must login each time.
I can propose a pa... -
10:12 Patch #4905: Redmine.pm: add support for Git's smart HTTP protocol
- Felix Schäfer wrote:
>
> ...
The thread http://www.redmine.org/boards/2/topics/15962 did help me. I was missing the trailing "/public" for the DocumentRoot field in my apache virtualhost.
Thanks.
-
09:43 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 the one column. E.g. by project and version, or by year and month in due date. Thank you. Petr
-
08:40 Feature #6118: Filter by parent task or subtasks
- +1
-
07:49 Feature #6118: Filter by parent task or subtasks
- Whoops - strike the bit in brackets "(as well as issues without any children)".
This is what I meant:
I want to be able to select parent task as a filter and say "Parent Task is null" - so that I get all top-level issues. -
07:42 Feature #6118 (Closed): Filter by parent task or subtasks
- There doesn't seem to be an option to use "parent task" as a filter. I want to be able to select parent task as a filter and say "Parent Task is null" - so that I get all top-level issues (as well as issues without any children).
-
07:37 Feature #6116: Group sub-tasks with parent on issue list
- Add "Parent Task" column to the issues list. Sort on parent task column. An arrow is placed for subtasks of a parent and grouped under it.
-
07:06 Feature #6116: Group sub-tasks with parent on issue list
- Actually looking at it, probably the easiest thing to do would be to use the group by functionality already in the system to group the subtasks
-
06:53 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.
Hav... -
07:28 Feature #643: Issue description templates
- Similar request to #2931.
-
07:26 Feature #6117 (New): subtasks default to parent issue target version
- I have been asked if it is possible to have subtasks default to the same target version as the parent when the "new issue" screen is opened or the parent ID is assigned.
-
06:50 Feature #5881: Subtasks do not always appear below the parent task in Gantt chart -> a job for a custom filter?
- In fact, I think the requests surrounding the issues list should be separated out from this issue which is originally raised against the gantt chart.
-
06:45 Feature #5881: Subtasks do not always appear below the parent task in Gantt chart -> a job for a custom filter?
- I think it is critical to be able to easily associate sub-tasks to parent tasks on the issue index page via something like indentation and grouping. An option to allow this would be very welcome
-
06:47 Feature #6115 (Closed): Parent issue id field in issue bulk edit.
- It would be very useful to be able to assign subtasks to a parent via the bulk edit screen.
Doubly so in the beginning since we have many people who have to re-organise their issues now that we have sub-tasks. -
04:33 Patch #2931: Templating for description of new tickets by Tracker
- We installed this latest patch on 1.0.0. and are able to configure different description templates for different trackers.
Upon creation of new issue, the description template for the default tracker is shown. However, when a differe... -
00:08 Feature #284: Issues fixed in multiple versions
- Felix,
You've closed this based on #219 but in the last entry, the author states the patch will most likely not merege into the current tree and that was 3 years ago. Is it a valid resolution at this point? It is still needed for sure.