victor wrote:admin wrote:List of improvements in 2.8:
User Interface
- Link-friendly URLs
What is this?
You can copy URL of any page (including reports or uploads), send this URL to your friend and he can open page directly in browser, no "Session has been expired" exception.
victor wrote:admin wrote:- All forms are printer-friendly
- Per-user default project
I see (I dont use now) that the user properties sheet had a "Default project" field in 2.7. Are you talking about it?
This property in 2.7 confuse users, because it wan not a property - this field allow easely users to ACL when you create user. In 2.8 this is odinary property - it store project name that should be selected after user login or click "Task Management".
victor wrote:admin wrote:- Support copy operation for workflows, filters, user groups.
- On-line help
- Quick task search by keyword
Is it the editbox up-right the subtasks list?
Not exactly - in editbox you can find task by number or by alias. I am about editbox on "Subtasks" page, it search keyword in tasks that return specified filter.
victor wrote:admin wrote:Task Management
- Numeric Task Numbers
- Calculated custom fields
- Support bulk edit for task budget, deadline and priority
Can I disallow that a user can change the task priority with this bulk edit?
Yes, of course - just remove MESSAGE_SCHEDULER (or TASK_SCHEDULER, I don't remember) role.
victor wrote:admin wrote:- Longtext description and message support
- Submitter&Handler feature in Categories and Transition rules
- Modify now means "modify after create"
- Start of task description has been added to task header
- More easy fill "Edit Category" and "Transition" pages
I see that you are added a combolist but I understand it very well. Could you explain one or two of this combos?
When you select something in the row header - it change values for row.
When you select something in the column header - it change values for column.
When you select something in the upper left coner- it change all values.
victor wrote:admin wrote:- Perfomance of "change parent task" operation has been improved
- "Expire date" has been added for users
I see the user registration sheet but I dont understand it, any tip?
I hope, that following help you:
----------------------------------------------------------------------
Summary
TrackStudio can be configured in such a way that the new user registration will be possible without the participation of the system administrator. In that case users can register with the system on their own and gain access to certain tasks.
Description
The registration settings are stored in the file trackstudio.register.properties, and are also available via the Server Manager on the Registration tab. You can use the following configuration parameters:
trackstudio.registration – specifies whether the external user registration is allowed. Possible values: yes, no. If the parameter is set to yes, a user sees the additional Register button on the login page. Using this button he/she can access the registration page. If the parameter is set to no the user will not be able to go to the registration page.
The following parameters for a new user are available:
registration.user – specifies the ID number of the user parent to new users. For example, for new users to be able to register as child users of the root user, you should set this field to 1 (Admin ID).
registration.prstatus – specifies the status ID of the new user. For example, the ID number of the manager status is 1, while the ID number of the tester status is 3.
registration.childs – specifies the maximum amount of sub-users that the new user can create.
registration.expireindays – specifies the number of days after which the created account expires. If the parameter is not specified or is set to 0 there will be no time limitations for the new users to use their accounts. In that case the account will expire when/if one of the parent users’ accounts expires.
You should specify the project or task the new user has access to:
registration.createtask – specifies whether a new task is created for the new user or whether he/she is granted access to an existing task. Possible values: yes, no. The yes value is usually used when organizing a hosted service, when tasks for different self-registered users should be independent. In this case a new task is created and the new user is granted access rights to it. The no value is used to allow customers to register with the system and to enter the information about bugs for an existing project. The ID of the latter is specified in registration.acltask.
registration.parenttask – specifies the ID of the task that will be the parent to a new task of the user.
registration.category – specifies the ID of the category for the new task. For example, the ID of the project category is 1, while the ID of the bug category is 2.
registration.acltask – specifies the ID of the existing task the new user is granted access to. In this case no new task is created.
The status specified in registration.prstatus should be available for the user specified in registration.user. The category specified in registration.category should be available for the task specified in registration.parenttask. The values of all parameters are checked at the system start. If any parameters are incorrect TrackStudio will stop running. You can learn about what caused the error from the message text. To solve the problem you must correct the value of the invalid parameter and restart TrackStudio.
Example
Example 1. Suppose we need to organize a hosted service. To do that, new users with the manager status (ID 1) should register with the system. Their parent user should be Admin (ID 1), they should be allowed to create 2 sub-users and to use their account for 30 days, and they should have their own project for creating subtasks.
In this case the parameters should be set as follows:
trackstudio.registration yes
registration.user 1
registration.prstatus 1
registration.childs 2
registration.expireindays 30
registration.createtask yes
registration.parenttask 1
registration.category 1
Example 2. Suppose we need to grant customers access to the information about bugs in the system being developed now. To do that, new users should register with the system under the tester status (ID 3) and have Admin (ID 1) as their parent user. They should not be allowed to create sub-users, there should be no time limitations to the use of their account, and they should have access to the project with ID number B01AE0FC4191AF12E0306BD990BC046A.
In this case the parameters should be set as follows:
trackstudio.registration yes
registration.user 1
registration.prstatus 3
registration.childs 0
registration.expireindays 0
registration.createtask no
registration.acltask B01AE0FC4191AF12E0306BD990BC046A
------------------------------------------------------------------
victor wrote:admin wrote:Filters
- Filter by submitter or handler group
- "Last x messages" feature in message filter
Where can I find this feature?
Check out Filters->Edit->View Messages/Filter Messages options.
victor wrote:admin wrote:Email submission
- Per-project email submission rules
What are you talking about?
Now if somebody send simple email to TrackStudio it can be imported as new task or message. Please check out Task->E-mail import page.
victor wrote:admin wrote:- Import emails as new tasks or messages
Where can I read some thing about this? How can I send an importable email? What format must to have it?
Alpha version has no documentation, sorry. But rules are following:
1) Only messages from exists users can be imported (we check email in database).
2) User should have access rights to access project.
3) You should enable mail import for some task and send message to TrackStudio.
4) In a minute it should create new task of specified category, set custom fields to default values, upload attachments and send email notification. No special requirements for e-mail format, this feature should be useful for customer support.
5) Email notification include task number now - just repy to it (or send mail with task id in subject) and TrackStudio will add this message to task. But this feature broken in alpha version, it should be fixed in beta (early next week).
victor wrote:admin wrote:- LDAP integration
In another message I ask you about any tip to use it with MS Active Directoy if you know about it.
Yes, we test it with Active Directory and it works fine. It should be quite easy to configure:
--------------------
Summary
A lot of organizations use the LDAP directory to store user accounts. TrackStudio can be configured to authorize users by their accounts on the LDAP server.
Description
The LDAP settings are stored in the file trackstudio.ldap.properties, and are also available via the Server Manager on the LDAP tab. You can use the following configuration parameters:
trackstudio.useLDAP – specifies whether the authorization on the LDAP server is used. Possible values: yes, no. If the parameter is set to yes, the user authorization on the LDAP server will be performed along with the usual authorization in the TrackStudio system.
ldap.host – specifies the LDAP server address (e.g. 192.168.22.10).
ldap.port – specifies the server port (e.g. 389).
ldap.authby – specifies which of the user parameters is used for the authorization on the server. It can take one of two values: name or login. It shows which of the TrackStudio user parameters is used as the user name or user login when authorizing on the LDAP server.
Even if you use LDAP authorization, you will have to register a new user in TrackStudio first. This new user login (or name) must be exactly the same as those on the LDAP server. By default, the user login is used for the authorization, so if you want to use the user name, make sure that the ldap.authby parameter is set correctly. Thus, the user can log into the system if the submitted password is equal either to that stored on the LDAP server or that stored in the local database.
-----------
victor wrote:admin wrote:- User self-registration rules
Is it related with the User register in trackstudio server manager?
Yes
victor wrote:admin wrote:Other
- Based on Hibernate 2.0, JasperReports 0.5.0
Could you give me a tip about what is this?
Nothing special, we just upgrade version for our persistence engine and report generator. Also, we fix many problems with reports quality (especially, PDF) and custom field support.
victor wrote:admin wrote:- Check database integrity at startup
- Support transfer data between DBMSs via XML import/export
How can I use it? Can I export my production oracle database (2.7) and import it in my test hsql database?
No, you can't use import/export to upgrade. You should upgrade to 2.8 your oracle database, export it and import it to HSQL.
Thats all...
victor wrote:About all the other things and more others I only can say that you are doing a big and excellent job. You are added more useful improvements and every day TrackStudio confirm that it was a right purchase for our company.
Cheers!
Thank you! Can I add your words to your testimonial ?
