Skip to content

Conversation

@jero-odoo
Copy link
Contributor

This PR updates the "Allow customers to close their tickets" document. The title has been changed to "Closing Tickets" to reflect new content. Added sections for manually closing tickets, and automatically closing tickets. Updated the closure by customers section, updated information about closing stages (now 'folded stages'). Updated screenshots and terms to reflect 16.0 changes. Removed obsolete section on reporting filter ("closed by partner").

@jero-odoo jero-odoo self-assigned this Feb 22, 2023
@robodoo
Copy link
Collaborator

robodoo commented Feb 22, 2023

@C3POdoo C3POdoo requested a review from a team February 22, 2023 19:53
@jero-odoo jero-odoo requested a review from brse-odoo February 22, 2023 19:54
Copy link
Contributor

@brse-odoo brse-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jero-odoo, I've finished my review of this doc rewrite. Great job! I only had a few minor suggestions for language throughout. Feel free to ping me with any questions, thanks!

@jero-odoo jero-odoo force-pushed the 16.0-helpdesk-update-close-tickets-jero branch from 714b6dd to 919ca8a Compare February 23, 2023 14:00
@jero-odoo jero-odoo removed the request for review from StraubCreative March 16, 2023 12:21
@jero-odoo jero-odoo force-pushed the 16.0-helpdesk-update-close-tickets-jero branch from 919ca8a to 474d254 Compare March 16, 2023 16:03
@jero-odoo jero-odoo requested a review from tiku-odoo March 16, 2023 16:08
Copy link
Contributor

@tiku-odoo tiku-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jero-odoo Great work on this doc. I've made a few suggestions. I did use a guilabel on "Stage" as this is referring to something in the UI. I've also added a few other labels. Let me know if you have any questions. Thanks! Looking forward to seeing this published. 👍

@jero-odoo jero-odoo force-pushed the 16.0-helpdesk-update-close-tickets-jero branch from 474d254 to 42ec8b8 Compare March 23, 2023 13:21
Copy link
Contributor

@samueljlieber samueljlieber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @jero-odoo! Great job on this doc, I've made some technical changes below for your reference. I'm approving these changes right away because they are so small and sending to final review!

Closing tickets
===============

Once work has been completed on a :guilabel:`Helpdesk` ticket in Odoo, there are several ways it can
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can italicize helpdesk ticket.

===============================

As work on a ticket progresses, it is moved along to the next stage in the pipeline. Once the issue
is solved, the ticket is moved to a :guilabel:`folded` stage. This marks the ticket as *closed*.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can italicize folded stage.

As work on a ticket progresses, it is moved along to the next stage in the pipeline. Once the issue
is solved, the ticket is moved to a :guilabel:`folded` stage. This marks the ticket as *closed*.

To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and click on a :guilabel:`team`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

capitalize :guilabel:Team

@samueljlieber samueljlieber force-pushed the 16.0-helpdesk-update-close-tickets-jero branch from 42ec8b8 to eee0b25 Compare March 29, 2023 17:01
@samueljlieber
Copy link
Contributor

Implemented technical changes in eee0b25 and approving for final review @StraubCreative.

@StraubCreative StraubCreative force-pushed the 16.0-helpdesk-update-close-tickets-jero branch from eee0b25 to 3b2db5b Compare April 11, 2023 00:22
Copy link
Contributor

@StraubCreative StraubCreative left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jero-odoo
Great doc. Nice job! 🎉
I have a few small suggestions below around tense and specificity/wording, which I just pushed up on 3b2db5b.

  • If you approve of the changes, you can issue the merge command [at]robodoo r+ and it will merge right away; or
  • If you have further changes to make, pull down the latest commit to your local machine by using git pull --rebase and then Re-request Review (the little 🔄 icon) after pushing back up your revisions. We can also revert all of my changes to your prior commit if you'd prefer (if so, I can show you how to do that).

Thanks!

@robodoo delegate+

Closing tickets
===============

Once work has been completed on a *helpdesk ticket* in Odoo, there are several ways it can be
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Think it makes the most sense to indicate that the ticket belongs to Helpdesk, the app.

Suggested change
Once work has been completed on a *helpdesk ticket* in Odoo, there are several ways it can be
Once work has been completed on a *Helpdesk* ticket in Odoo, there are several ways it can be

Comment on lines 11 to 12
Manually closing solved tickets
===============================
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simple present > continuous tense.

Suggested change
Manually closing solved tickets
===============================
Manually close solved tickets
=============================

Comment on lines 17 to 19
To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and click on a :guilabel:`Team`
to open the pipeline. Choose a stage, and click on the gear icon at the top right of that stage's
kanban column.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Team doesn't get a guilabel here since it's not the name of a field, label, button, etc. on the UI.
Slight wording change around the gear icon too since it only appears when hovering over the stage name (and isn't immediately visible).

Suggested change
To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and click on a :guilabel:`Team`
to open the pipeline. Choose a stage, and click on the gear icon at the top right of that stage's
kanban column.
To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and click on a team to open the
pipeline. Hover over a stage's heading, and then click the gear icon that appears in the top-right
corner of that stage's kanban column.

Comment on lines 31 to 32
Select :guilabel:`Edit Stage`. This will open the stage's settings. Check the box labeled
:guilabel:`Folded in Kanban` towards the top of the window. :guilabel:`Save & Close`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indicate that a menu appears after the gear icon is selected.
Would form a compound sentence, as well, to link setting/save actions together.
Also added a conclusion to iterate cause > effect.

Suggested change
Select :guilabel:`Edit Stage`. This will open the stage's settings. Check the box labeled
:guilabel:`Folded in Kanban` towards the top of the window. :guilabel:`Save & Close`.
From the menu that appears, select :guilabel:`Edit Stage`. This will open the stage's settings.
Check the box labeled :guilabel:`Folded in Kanban` towards the top of the window, and then
:guilabel:`Save & Close` to confirm the changes. Now, tickets that reach this stage will be
considered as *closed*.

:align: center
:alt: Stage settings page.

Automatically closing inactive tickets
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simple present > continuous tense.

Suggested change
Automatically closing inactive tickets
Automatically close inactive tickets

Comment on lines +44 to +47
Go to the team's settings page by going to :menuselection:`Helpdesk --> Configuration --> Teams`.
Under the :guilabel:`Self-Service` section, enable :guilabel:`Automatic Closing`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The first way is correct.
Another way to write this so it's a compound sentence with time-order language.

Suggested change
Go to the team's settings page by going to :menuselection:`Helpdesk --> Configuration --> Teams`.
Under the :guilabel:`Self-Service` section, enable :guilabel:`Automatic Closing`.
Enable automatic ticket closing by first navigating to :menuselection:`Helpdesk --> Configuration
--> Teams`, and then under the :guilabel:`Self-Service` section, enable :guilabel:`Automatic
Closing`.

due to assignment or workload issues. Closing these tickets automatically would result in issues
going unsolved.

Therefore, the :guilabel:`Automatic Closing` settings would be configured as below\:\
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Images are only supplemental to the writing; the writing needs to stand on it's own.
Actually write this part out 😉

Suggested change
Therefore, the :guilabel:`Automatic Closing` settings would be configured as below\:\
Therefore, the :guilabel:`Automatic Closing` settings would be configured as below\:\
- :guilabel:`Automatic Closing`: *checked*
- :guilabel:`Move to Stage`: `Solved`
- :guilabel:`After``7`:guilabel:`days of inactivity`
- :guilabel:`In Stages`: `Customer Feedback`

Comment on lines 81 to 82
Allowing customers to close tickets
===================================
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simple present tense.
Slight rewording so we're not (unintentionally) indicating that customers can close any other tickets that are not their own 😉

Suggested change
Allowing customers to close tickets
===================================
Allow customers to close their own tickets
==========================================

Comment on lines 84 to 85
Enabling the :guilabel:`Closure by Customers` setting allows customers to close their own tickets
when they determine their issue has been resolved.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing determiner, that.
Would surround the s in parenthesis otherwise there's a plural/singular mismatch.

Suggested change
Enabling the :guilabel:`Closure by Customers` setting allows customers to close their own tickets
when they determine their issue has been resolved.
Enabling the :guilabel:`Closure by Customers` setting allows customers to close their own ticket(s)
when they determine that their issue has been resolved.

:alt: Customer closing setting in Odoo Helpdesk.

Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` button will be available
for customers when they view their ticket.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specificity.
Where exactly does this button appear?

Suggested change
for customers when they view their ticket.
for customers when they view their ticket through the customer portal.

@jero-odoo
Copy link
Contributor Author

Thanks @StraubCreative, the changes look good. I will merge

@jero-odoo
Copy link
Contributor Author

@robodoo r+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants