Activity
From 2010-04-23 to 2010-04-25
2010-04-25
-
23:24 Patch #4861: Translation update for Russian locale
- Ivan, see #5157.
-
17:32 Patch #5379: Updated Polish translation for 0.9.4 / trunk
- Please consider -pl-trunk.diff- outdated, use *pl-trunk2.diff* instead. Thanks!
-
13:34 Patch #5379 (Closed): Updated Polish translation for 0.9.4 / trunk
- I attach an update to pl.yml, after contacting one of the current translators.
Here I improved some spelling, added missing strings, and more forms of some words (for example, "few:" form in addition to "one:" and "other:" forms).
On... -
17:14 Feature #2653: New permission for issues: view_own_issue
- It might be only terminology.
And i can see a point of being able to have both private and public issues in same project. Some helpdesk issues you may want to show to everyone but only after you first saw them (as private).
Also us... -
15:31 Feature #2653: New permission for issues: view_own_issue
- Unset "Add issue" to all
Set "Add private issue" to all
-
14:43 Feature #2653: New permission for issues: view_own_issue
- enough => is enough
-
14:42 Feature #2653: New permission for issues: view_own_issue
- Oleg Volkov wrote:
> Set "Public" for Helpdesk project, unset "Public" for IT Tasks projects.
> ...
I got it, but I'm still not sure what the reason to do two types of issues (private and not private) when just only one enough? -
14:32 Feature #2653: New permission for issues: view_own_issue
- Set "Public" for Helpdesk project, unset "Public" for IT Tasks projects.
Unset "Add issue" for "Not member".
Set "Add private issue" for "Not member".
Set "View private issue" for "Developer" (for view all private issue).
-
14:12 Feature #2653: New permission for issues: view_own_issue
- I'm not sure how can one use "Private tasks". You can use private project instead.
For example: I have two projects: IT Tasks (primary) and Helpdesk (child project).
Primary task is private - just only for IT team. Helpdesk - public pr... -
13:55 Feature #2653: New permission for issues: view_own_issue
- Why?
-
13:43 Feature #2653: New permission for issues: view_own_issue
- Oleg Volkov wrote:
> #337 is able to work, please test it
I believe that it should work. Nevertheless it's really more than necessary. "View own issue" and "Create an issue" permissions would be enough I think. -
12:12 Feature #2653: New permission for issues: view_own_issue
- #337 is able to work, please test it
-
12:00 Feature #2653: New permission for issues: view_own_issue
- Private issues looks like a little bit complex workaround for "view_own_issue".
-
12:00 Feature #2653: New permission for issues: view_own_issue
- External users (not member):
- not view other issues,
- view own issues
Developer users view all issues.
See #337 description and http://www.redmine.org/issues/2653#note-19 -
11:51 Feature #2653: New permission for issues: view_own_issue
- I will read up on your #337 and do some tests.
You might be right or i need to formulate my ideas better.
BR,
Thomas -
11:49 Feature #2653: New permission for issues: view_own_issue
- True, but we don't want them to be able to enter anything that can be seen by other users, no matter how they mark it.
All their issues should be isolated from each others and support-center can work with them all.
-
11:44 Feature #2653: New permission for issues: view_own_issue
- External users will NOT see each others PRIVATE issues.
-
11:35 Feature #2653: New permission for issues: view_own_issue
- The difference is that external users will see each others issues.
This is in alot of situations not desirable.
Currently we solve this with different projects per customer/user but would really like to make sure that each external... -
15:52 Feature #3945: Shorten revision ID for git events
- Also see #3244. A review of the patch included would be nice.
-
14:55 Defect #4278: Mysql::Error: Updated from 0.8.0 to trunk rev 3085
- If you had a failed upgrade/migration in the past you may need to rename the pre-existing member_roles and group_users tables. After a successful upgrade you can delete the member_roles_saved and groups_users_saved tables.
@mysql> re... -
12:54 Feature #296: REST API
- Thanks a lot.
-
12:09 Feature #337: Private issues
- |Permission|Non-private issue|Created private issue|Assigned private issue|Watching private issue|Other private issue|
|Unset "View issue"|Not view|Not view|Not view|Not view|Not view|
|Set "View issue" and unset "View private issue"|V...
2010-04-24
-
16:45 Feature #5239: privilege to assign an issue
- Maybe to hide the field "assigned to" for not_member?
-
07:46 Feature #4309: create a special role for clients
- You can create a subproject and for each issue the client to create a issue in the subproject.
-
07:37 Feature #4167: Issues access: to allow a user view ONLY issues that his is assigned on
- See #337.
Private issue is visible for:
- created
- assigned
- watching
-
07:18 Feature #3384: issue permissions
- See #337 or use subprojects.
-
07:13 Feature #2653: New permission for issues: view_own_issue
- What is different from #337 ?
#337 is already working
For external users (Not member):
- set "View issue"
- unset "Add issue"
- set "Add private issue"
- unset "View private issue"
For internal users (Developer, Manager):
- set "... -
06:50 Feature #4834: Java implementation of redmine API
- I created a draft version of Redmine Java API.
Sample Java Application to parse Redmine data and generate Microsoft Project file (includes Redmine Java API): http://redmine-connect.googlecode.com/files/redmine_connect.zip
I will kee... -
01:28 Feature #1385: Script for import from JIRA
- Have you updated the script with Marcel's patch? Also you probably want to run the rake command with --trace, to find out what line is causing the problem. Most likely is that you don't have trackers called Bug, Feature, and Task (see to...
-
00:42 Defect #3672: Unable to set "value" and "old_value" through :helper_issues_show_detail_after_setting hook
- Couldn't this issue be fixed quite easily by assigning the value, old_value, and label defaults before calling the hook in app/helpers/issues_helper.rb?
h3. Current
2010-04-23
-
22:45 Defect #5360: Report shows sub-projects for non-members
- Change affected version, I tested on trunk, and the error is the same.
Now I know I shouldn't set the "Affected version", won't do it next time. -
20:54 Feature #337: Private issues
- |Operation|"Add issue"|"Add private issue"|"Edit issue"|
|Can not create any issue |no |no |any|
|Create only non-private issue|yes|no |any|
|Create only private issue |no |yes|any|
|Create any issue |yes|yes|any|
... -
19:43 Feature #337: Private issues
- Juraj Soft,
Just set permission to add private issues and remove add normal issue
Then user will create private issue by default.
Private issue is visible for creator, assigned to and watchers -
19:36 Feature #337: Private issues
- We need to limit visibility of Issue just for creator and envolved people.
Possible solution:
It could be possible to set new permission _Create Private only_.
How it could work:
If user have role with this permission, every new ... -
17:10 Feature #337: Private issues
- Optimize code.
Fixed:
- pagination issue list
- visibility issue page in the xml / atom / pdf representations
-
20:27 Feature #408: Assign a task to multiple users
- I thoroughly disagree with Brad Mace's note above. I and thousands of other people at multiple telecom equipment manufacturers have used a variant of Scrum since before it was called Scrum. This school of thought might have been derive...
-
19:15 Feature #2850: Add next/previous navigation to issue
- +1
At my business we recently moved from Bugzilla to Redmine and the #1 questions I get from everyone is "there a next/prev link when you are going through your issues?"
-
18:53 Feature #2356: SSO Authentication (CAS Jasig)
- Whoops. Previous patch I attached had bugs on head. This patch applies cleanly, and should work perfectly. I'm also working on a few improvements to the logout process, but that requires changes to rubycas-client first.
-
06:09 Feature #2356: SSO Authentication (CAS Jasig)
- Attached is a patch which provides CAS functionality, along with settings to boot. Allows both forced and optional CAS login. Don't know if it's up to code standards, but it's a start, and I'm willing to work on it further. Developed ...
-
18:53 Defect #5378: Modified column in Issues view does not obey date format set in Administration > Settings > Display
- Update: If I mandate a time format rather than allowing that to be chosen based on the user's language, then the date format is reflected in the view.
So the bug appears to be that a system-wide date format is only used when the time ... -
18:51 Defect #5378 (Closed): Modified column in Issues view does not obey date format set in Administration > Settings > Display
- In Administration > Settings > Display I have date format set to 23 Apr 2010, and time format set to "Based on user's language".
However, when I go to a project and select the Issues tab, the Modified column shows (e.g.) 04/19/2010 04... -
18:24 Defect #2919 (Reopened): migrate_from_trac fails with "Tracker(#XXX) expected, got NilClass(#YYY)"
- Hallo!
I have similar problem!
But your advise doesn`t help me... -
17:28 Feature #1385: Script for import from JIRA
- Sorry. Were careless.
But have new problem.
After 10 second working script i recieved new error message...
Migrating projects.rake aborted!
Tracker(#-609467598) expected, got NicClass(#-604479008)
-
17:01 Feature #1385: Script for import from JIRA
- Thanks Charles L. Now, when i run migrate_from_jira.rake i have error message:
rake aborted!
undefined method 'get_values' for #<Class:0xb769eae4>
What`s the matter?
-
17:23 Feature #1572: Delete Users and automatically ticket change
- +1 We have the same problem, and have been manually cleaning the SQL DB since 0.7x
Maybe this could be split into two mini-features:
# Add @Delete@ choice to the *Registered* page view (today the only option remains: _Activate_)
... -
15:19 Feature #3816: Allow pasting screenshots from clipboard
- Hello,
I'm running the 0.9.trunk and have the same log as http://www.redmine.org/issues/3816#note-16
I'm trying to debug in NetBeans and I found this on line 49 in the init.rb plugin file: -
15:17 Defect #5373: Translation missing when adding invalid watchers
- Mmh, that's odd… Please provide the information listed in [[SubmittingBugs]] (especially the output of @RAILS_ENV=production ruby script/about@) and see if there is some meaningful error trace in the logs. We need to be able to reproduce...
-
15:06 Defect #5373: Translation missing when adding invalid watchers
- It seems like it is just one user in the project. My appologies.
-
15:03 Defect #5373: Translation missing when adding invalid watchers
- This might be part of translations but it is a bug as well - It will not allow me to add more then one watcher. Yes the error message shows the code but the logic itself is not working
-
13:31 Feature #5377 (Closed): проверить статистику
- Please use the "demo redmine":http://demo.redmine.org/ for testing purposes.
-
12:43 Feature #5377 (Closed): проверить статистику
- у всех провайдеров
-
12:42 Defect #5376 (Closed): не входит в домен
- Please use the "demo redmine":http://demo.redmine.org/ for testing purposes.
-
12:38 Defect #5376 (Closed): не входит в домен
- сарапул, РА
-
10:49 Feature #296: REST API
- @Lennard Hunfeld , @Javier Hernandez : you can use issue api to add spent hours to project ;)
-
10:22 Feature #296: REST API
- Hi,
we are having the same problem with the time tracking.
Is there actually a good way to add spent hours using rest? -
09:31 Patch #989: Migration task from Bugzilla
- > Ralph Juhnke wrote:
> ...
Well, I used option 2, and I was able to import things into database. Looks like most of redmine pages are working well now.
However when I navigate to http://redmine:3000/admin/projects and choose "All" ... -
00:27 Patch #989: Migration task from Bugzilla
- Eugene Dzhurinsky wrote:
> > You seem to have translated "bug severities" others than ( "critical", ..., "enhancement") in your bugzilla database. Can you check this?
> ...
Your data is correct :-)
Then we have two options:
1. C... -
08:55 Feature #5306: Separation of core and Redmine plugins
- I'm in support of separating core Redmine plugins and user-defined ones. This would make upgrading using tar.gz files so much easier. And we would not have to abandon engines, which would be a bad idea indeed.
The seperatio could be t... -
02:51 Feature #5306: Separation of core and Redmine plugins
- I don't like the idea of putting Rails plugins or Redmine plugins in a different path. It would be even more code that we would need to support and maintain (and with Rails 3, who knows what would break). I think Radiant went this path...
-
08:39 Defect #5375 (Closed): Roadmap "open" link jumps to child issue list, filtering out parent issues
- to reproduce:
# create a parent project with a child
# create a version for the child project, choosing "With project hierarchy" for the Sharing option
# create a issue for the parent and assign it to the child's version
# go to the... -
03:50 Feature #5361 (Closed): Next / previous issue feature
-
02:40 Feature #4955 (New): How to simplify the interface as much as possible