Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Ticket Statuses #1159

Merged
merged 19 commits into from Aug 22, 2014

Conversation

protich
Copy link
Member

@protich protich commented Aug 15, 2014

Continuation of PR #1094

@protich
Copy link
Member Author

protich commented Aug 19, 2014

Ready for final review.

@protich protich force-pushed the feature/custom-statuses branch 2 times, most recently from 83b254d to a5a965b Compare August 20, 2014 03:25
Only cache results for ALL items
Messages are extracted on post-action redirect.
If a comment is provided it's handled as an internal note - allowing for
alerts to be sent out (if enabled)
Move ticket status change to unified backend.
Fix cases where first item added via addSubMenu got deleted.
This allows for subclasses to define how the choice is formatted.
Split ticket status states into public and private
Reserve 'archived' state for automation
Statuses with tickets cannot be deleted
Fix orm to class gracefully when joins are not inspected
Add create date to new statuses
Delete tickets for realz when set to 'deleted' status. This commit will be
partially reverted once data retention plugin is added.
Empty the popup container and show loading spinner
on-load hide the spinner and show the content
Unify use of modal dialog
Make popup dialog graggable
Flags will be reimplemented as a separate feature.
Cleanup status change form
Add resolve to ticket ticket view
Use the new status table when checking for overdue
Staff can now select desired ticket status on create
Only allow staff with closing permission to set tickets to resolved state.
greezybacon added a commit that referenced this pull request Aug 22, 2014
@greezybacon greezybacon merged commit f97dfaa into osTicket:develop-next Aug 22, 2014
@Dorian-Grim
Copy link

I am confused. Wasn't this supposed to let users to create custom ticket statuses?
image

@ntozier
Copy link
Contributor

ntozier commented Dec 12, 2016

@Dorian-Grim this is a Pull Request from 2014. It was merged with develop-next on Aug 22, 2014.
The feature [The ability to create custom ticket statuses] has been part of the project for over 2 years, starting with version 1.9.4 (which was released on Oct 27, 2014). I perhaps if you have a question you should ask it on the forums. If you have a bug that you can replicate then report it by opening an issue.

@Dorian-Grim
Copy link

Well I was on 1.10 and I couldn't or didn't know how to create custom statuses...

@ntozier
Copy link
Contributor

ntozier commented Dec 12, 2016

If you have a question please ask it on the forums.
If you have a bug that you can replicate please report it by opening an issue.

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.

None yet

4 participants