Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

Notifications
Clear all

Questions

3 Posts
2 Users
0 Reactions
3,590 Views
DEDIEU
(@jcde)
Posts: 104
Active Member
Topic starter
 
[#911]

Question about ticket
When entering the work on the tickets, the calculation of hours to the assignment can create an error if you consume more than one day: All times are reported on the same day and thus create an error

When creating a ticket is obliged to register to add a piece attached. Possible to to add a piece attachment before saving?

stop script
Is it possible to stop scripts loading? ex schedule

Risks & acttion
Risks or actions can not be shared by teams or clients.
Is it possible to define rights a function of a type of risk or action?


 
Posted : 23 Jan 2013 13H45
(@babynus)
Posts: 14952
Member Admin
 

When entering the work on the tickets, the calculation of hours to the assignment can create an error if you consume more than one day: All times are reported on the same day and thus create an error

It is not really an error : it is just an overload of work on a given day. The error is to enter several days of wrok in one time : best practice is always to enter wxork day by day (so work entered one day will not be more the resource capacity). In this case, the error in behind the keyboard 👿

When creating a ticket is obliged to register to add a piece attached. Possible to to add a piece attachment before saving?

Already requested (Ticket #61). It may be really usefull but implies to reconsider complete tool framework. Will not be high priority.

stop script
Is it possible to stop scripts loading? ex schedule

No it is not possible.

Risks & acttion
Risks or actions can not be shared by teams or clients.

Yes they can.

Is it possible to define rights a function of a type of risk or action?

No, it's not possible to define visibility depending on type of risk or action. Visibility is always base on Project. What you may do is define specific sub-projects : one for client visivility, one for private team visibility. Team can then be affected to top project, to see both. Client is only affected to sub-project get s limited visibility.


 
Posted : 24 Jan 2013 11H37
DEDIEU
(@jcde)
Posts: 104
Active Member
Topic starter
 

you're right I had not thought about the external project solution
Tanks for your support 😉


 
Posted : 25 Jan 2013 0H21
Share:

Scroll to Top