| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Also:
- creation of a (archived by default) sample project with tasks, that the
user can activate to discover the project app.
- improvement of the simplified form view to create a new project
|
|
|
|
The author_id field is actually a res.partner, not a res.users.
In some cases, if the partner with id 1 is deleted, installing
project was impossible.
|
|
|
|
|
|
But this should probably move to demo
|
|
|
|
|
|
The sentence was strange..
Closes #9595
|
|
workaround
The project and sale_timesheet modules both define a project_time_mode_id field on res.company but they are not dependent on each other. This causes problem because the first module that creates the field "wins" the xmlid and will delete the field on uninstall, regardless of the other module (which will then stop working until you do an update that will recreate the field).
To work around this in a stable version, we manually create xmlids for the field in each module; on uninstall the field will not be deleted if an xmlid still refers it (which will be the case if the other module is installed).
Inheriting fields from modules that are not dependent in a direct way (ancestor-child) is not supported, so normally you should use modularity to define the field in a parent module. Since 9.0 is a stable version, we need a small workaround.
|
|
|
|
|
|
|
|
|
|
|
|
We don't want the dispayed image to be set to the last attached image but we want to be able to choose it.
|
|
|
|
|
|
|
|
|
|
Major changes:
- New start and expiration dates
- Remove field Contract Status
- Simplified because use of sale_timesheet
Reason: complete rewrite of the Sale module.
Responsible: fp, dbo, nim
|
|
Followers can now be partners or channels. Partners following a document
will receive needaction, as previously. However people can follow documents
through channels. Members of a channel are able to listen to a stream
of messages using the channel. Those messages do not create needaction
messages. It is therefore possible to follow documents without receiving
too much notifications. For interesting documents subscribing with its
partner will create notification.
message_follower_ids fields is udpated. It is now a many2many to
mail.followers, not to res.partner anymore. A subscription can be either
a partner (partner_id) or a channel (channel_id).
Some access rules have been updated accordingly.
|
|
Move tag_ids in the task form
|
|
|
|
concept of default / common stages.
However as the link between stages and projects is still a many2many
it is still possible to have shared columns. It is however not the
standard way of using stages.
|
|
model has been renamed to mail.channel to prepare the slack modeling.
In future commits the mail.group model will be merged with the channel
model from im_chat. The first move is to rename mail.group into
mail.channel to have a model that will unite both features.
|
|
|
|
_track is now a method that returns the subtype to trigger in a given
tracking context. A tracking will now lead to only one subtype
being trigerred, instead of having multiple possible subtypes.
Now, one tracking leads to one message with one subtype, or without subtype
if there is none matching. This simplifies the model for future evolution of
chatter and mail.
[IMP] project, project_issue: cleaned task and issue subtypes, now having
opened for created / assigned.
|
|
next stage
|
|
- stage model (project.task.type): add fields holding the eventual specific
legends for kanban states and star (priority) management
- project: task now have labels; you may use project to hold trainings
instead of tasks.
- project form: use label field on tasks statinfo to use the label
- project.task form: use kanban state customization using states_legend option;
- project.task kanban: use kanban column and kanban state cuztomization
using group_by_tooltip and states_legend options
- project_issue: issues now have labels, like tasks.
- issue: same kanban custo as for tasks
- update data and demo data
[IMP] web: statinfo widget now take an optional label_field option allowing
to have strings coming from another field present in the form view
|
|
|
|
- project kanban view: dashboard-like view, add sparklines for open tasks
and closed issues
- project: cleaned demo data, less stages
- project: description is now an html field
|
|
kanban views
bzr revid: tde@openerp.com-20140508152536-s3my5onl33z3kxxx
|
|
bzr revid: mba@tinyerp.com-20140228131855-obhatiecnzv1bgqu
|
|
bzr revid: mba@tinyerp.com-20140221134423-sitdnyq3bcbidka3
|
|
bzr revid: tde@openerp.com-20140221112704-lqd4o5bnljn84yxs
|
|
bzr revid: sgo@tinyerp.com-20140210052655-efiwytz5kllk7irx
|
|
bzr revid: chs@openerp.com-20131124200937-0hwd527qxuaezic5
|
|
odo@openerp.com-20131121153230-keie85rmes2zh2o8
bzr revid: chs@openerp.com-20131121112139-aw2ara1i1xymue62
bzr revid: odo@openerp.com-20131121154205-ul9hf9tz3h0x2n7m
|
|
stages, exclude mail.message.subtypes (want overwrite), courtesy of Alex Comba (Agile BG)
lp bug: https://launchpad.net/bugs/1172149 fixed
bzr revid: mat@openerp.com-20131120151439-96l2z98tebj46fzs
|
|
After some experiments, having colors does not seem to give an
usable result on statusbar widget. Indeed we need to have the
current stage highlited, and maybe something to tell that some
stages have a special meaning and/or are the end of the pipe.
The closed field already gives that meaning.
Moreover the issue with the statusbar widget is that it indicates
state and action. Having both dimensions with colors / icons
is quite difficult to understand. We therefore stand on a simpler
version of the widget, only with stages and the current stage
highlighted.
bzr revid: tde@openerp.com-20131021104912-8ybhw0svdoghheh3
|
|
- stages: added some fields
-- closed: indicates whether this stage close the working process, for
example task ended, lead lost, applicant hired
-- bar_fold: whether to hide the state in the statusbar; this is different
from fold that is used for kanban views. Viewing a pipe or a specific
record are effectively different things and should use different fields.
-- bar_color: field to customize the stage in the statusbar (still WIP)
- impacted addons: crm, project, project_issue, hr_recruitment
- removed 'closed' addition in project_mrp as this is now in base project
module
bzr revid: tde@openerp.com-20131018132120-h0pv01q2bagtp99x
|
|
bzr revid: sgo@tinyerp.com-20130722064546-5algtla91hpnaanb
|
|
Removed concept of state on project.task (and propagated report)
Removed python inheritance towards base_stage (specific code will be re-added)
bzr revid: tde@openerp.com-20130626132519-988nfq8pw8h8c8e8
|
|
bzr revid: fka@tinyerp.com-20130516101202-ymh0wz1nfdx7zv27
|
|
bzr revid: cga@tinyerp.com-20130424101119-pzug9rqt8k7vhc6u
|
|
bzr revid: jco@openerp.com-20130321162939-gmwxjp6f444orh5f
|
|
avoid spamming contact partners.
bzr revid: tde@openerp.com-20130130090942-duiwfvtcj2d0ad6c
|
|
bzr revid: tde@openerp.com-20121219212330-xfx3lykstl1nsa8m
|
