Lien de vérification des travaux à venir et en cours

Vérification des taches en cours

Pour commencer si ce n'est pas déjà fait vous devez avoir un compte avec votre adresse email310-412-7518

Pour créer un compte... il faut savoir que les comptes sont soumis à approbation de l’administrateur, pour créer un compte, il faut imaginer son pseudo, avoir un mot de passe, et saisir les infos dans le formulaire en lien ici /questions-tbi.org/account/register

Pour faire une demande ou signaler un BUG(717) 503-4146

c'est vraiment facile, suivez ce lien 785-318-6632

Pour répondre à une demande ou signaler la résolution d' un BUGKababish

c'est vraiment facile, suivez ce lien 5405804289

Pour enregistrer vos temps d'interventionbumper

il y a quelques règles, suivez ce lien 917-757-4108

Pour le reste ...

How it works2019138627

When receiving an email, Redmine uses the From address of the email to find the corresponding user. Emails received from unknown or locked users are ignored.
If the email subject contains something like "Re: [xxxxxxx #123]", the email is processed as a reply and a note is added to issue #123. Otherwise, a new issue is created.
Note that, in order to create an issue, all required custom fields must be provided. Without them, issue creation will fail. As an alternative you can ensure that every custom field has a default value which is then used during issue creation.

Target project

The target project can be specified using the project option when receiving emails. This should be the identifier of the project and not the name. You can easily find the identifier in the url.
If you don't use this option, users have to specify in the email body which project the issue should be added to. This can be done by inserting a line in the email body like this: "Project: foo".
h3. Example (email body):
This is a new issue that will be added to project foo. Here we have the issue description [...] Project: foo
You can set a default project using the project option and let users override this default project by using the allow-overrideoption when receiving emails.
Example: # Create issues on project foo by default rake redmine:email:receive_imap [...] project=foo allow_override=project
Of course, user permissions are checked and this email would be ignored if the user who sent this email is not allowed to add issues to project foo.
Make sure that the target project doesn't use required custom fields with no default value for its issues, otherwise the creation of the issue will fail.

Example keyword list:
• Project
• Tracker
• Category
• Priority
• Status
• Start date
• Due date
• Target version
• Estimated hours
• Done ratio
• <Custom field name>

The values available are the ones of the context. E.g. Status available (for this Tracker and this Project) are labels in the localized language, exactly as displayed in the user interface or system default language (even with spaces, without quoting).
Example (email body):
This is a new issue that overrides a few attributes [...] Project: foo Tracker: Bug Priority: Urgent Status: Resolved
The format for keywords differs from the allowed attribute values for the allow_override option:
• project
• tracker
• status
• priority
• category
• assigned_to
• fixed_version (aka. Target version)
• start_date
• due_date
• estimated_hours
• done_ratio

Target Project from Email Sub-Address(504) 421-4207

This feature was introduced in ver 3.2.0 (SVN rev r14687). It may be preferable to have one mailbox for all incoming emails to a Redmine instance, instead of one per project. For some history of this feature see MailhandlerSubAddress. When receiving emails at , an email sent to will cause the issue to be added to project with identifier foo.
To enable this feature add the project_from_subaddress= to the command e.g.
rake redmine:email:receive_imap [...] project_from_subaddress=
If a project is included in the command-line then it becomes the default project that will be used for emails sent to . So with the command:
rake redmine:email:receive_imap [...] project=bar project_from_subaddress=
emails to or will raise issues in project bar; emails to will go into project foo.
Some email providers include support for sub-addresses, as per RFCs 3598, 5233. Where this is not supported, forwarding mail addresses to the 'central' address, may work (it does in my case), ie set up an email address forwarding all mails to from , etc. This is easy to administer and does not require fetching emails from multiple accounts, each with its own account credentials.
Issue attributes
Based on the options you use when receiving emails (see allow-override option), users may be able to override some attributes when submitting an issue.
Note: prior to Redmine 3.2.0 (#20543) some attributes were always overridable, but this was not documented. This behavior has been changed and all attributes have to be explicitly listed with the allow_override option to be overridable. For those who want all attributes to be overridable, allow_override=all can now be used (#20543).
Once allow_override has been configured, you can override those attributes by using the appropriate keywords in the email body.