"Opened" vs "Closed" tickets

Hello Jirka,

Every topic/ticket in the system can have different states, and some of them are open and closed. The progress is measured in different way for topics and tickets:

• Topics - statuses give the real situation about the progress of any idea, problem or question. By changing status we define that topic is still opened or closed. The state is connected to status in Administration area;
• Tickets - state is the parameter that defines the progress and it's more vital for the ticket then progress of it. It could be either opened or closed. Statuses here are only secondary parameter to check on what phase the progress is while it's opened.

We'll fix the problem with statuses management on Administration area for tickets, as statuses and states shouldn't be connected there.

Let us know if you have more questions or suggestions here.

Hello Stas,

thanks for information.

I have to then ask - isn't more clear to make it work in same way for topics as well as for tickets? Because that's what I expected and that really confused me. I expected, that when I mark "ticket" as "Solved", ticket will be correctly marked as "Completed". Then button "Complete" at top of every ticket really confused me.

Same it's when I answer to ticket - at bottom are two choices. One say "Opened", "Completed" and second allows to choose from list of "Statuses". And to be true, this confused me even more.

Take this as user feedback and idea for brainstorming. From my point of view, I just don't see clear reason, why have separate system for topics vs tickets. Thanks for listening.

Help Desk and Feedback systems are different in each usage and approach.

When you have "Problems" in feedback system, it's more likely to show users the progress based on Statuses. So statuses define if problem is opened or completed.

In Help Desk - tickets are managed only by state, and no matter what status is defined, as it's only indicator for agents on what phase ticket is located when opened. And what really matter here for user and agent, if ticket is opened or completed, so we give the option to change state of the ticket either for author or agent.

In other words, for topics the main parameter is status, for tickets it would be state. In topics statuses are beneficial for users, and in tickets statuses are designed only for agents.

We'll try to improve the system in the next few releases, so it would be more clear for agents to use both systems.

Good day Stas, thanks for description.

I've tried to understand more precisely with Peter (my colleague), how you system works.

And sorry, but we are still really confused. I'm still unable to understand, why I need to set completed ticket to status: "Solved" and some weird second state to: "Completed" (thanks to "Complete" button), to be able to filter completed tickets.

Please, during your next brainstorming, give this task few minutes and think about reducing amount of possible states from two (first: new, waiting for reply, solved, ... second: opened, completed) to just simply one (ideally first, where "solved" or other defined by user, will be consider as "completed").

Thank you!

Jirka, We've decided to remove "Solved" Status from tickets, as it's really confusing for agents.

Please read my previous comments. Tickets - main indicator is "State" - Opened or Completed. Statuses in tickets that show for agents where opened tickets are located and user doesn't care about these statuses. He should have his ticket resolved or answered, so it could be completed.

We are working on more improvements with help desk module, so it has own and easy to understand approach.