osTicket Development Status

Thank you for the update @protich! Sorry to here about @greezybacon.

Hi @protich

It's good to hear from you, and I'm sure the community will thank you for letting us know the situation on this project.

It is a real shame to hear about @greezybacon , he has been really helpful with us and getting additional features working etc.

I'm glad to hear his departing has been done nicely with him still contributing to this project.

We all look forward to the up and coming release and thank you.

Thanks @protich is a great news, and thanks a lot @greezybacon for your contribution

Great to finally hear about the 1.10 version being finalized and there are several developers joining the team, even though it's sad to hear @greezybacon left.

Btw. Wish you all the best @greezybacon for your future and happy to hear you're still helping out from time to time :)

Since we have a similar situation in my company, where a third of my colleagues left our team (or better: had to leave due to decisions which were taken for our team and even our team manager), I totally can understand that it takes a while to fill the gaps they left behind and there's a lot more work for the rest of the team. So wishing you @protich and the whole @osTicket team and supporters like @ntozier all the best and I'm hoping confidently you'll come like phoenix out of the ashes ;)

Btw. who ever is taking over Jared's part of taking care for the osticket translations, me and I also guess @mfelber will continue to support with the German translation. Btw there's still some larger pull request open from me #3027 to resolve mistakes in the sources and unify some phrases, so don't be shy and get in touch (who ever is taken over translation related stuff) since that PR should help all translators and proofreaders for faster and easier translations.

Cheers!
Michael

Thank you @protich,

for the update, and please accept my apologies if you feel our discussion about the fork did spam your project. Personally, I think an open communication is always more helpful than staying silent. given the current situation, I do appreciate that informing community devs is probably currently not your greatest concern. Nevertheless, I also believe that a more pro-active communication had made many comments obsolete.

As such I would appreciate a timely announcement of the above mentioned new framework so that efforts in the community can adapt quickly. Having said that, I'm looking forward for the new releases and also an open and appreciative cooperation.

All the best for you and your staff,
Martin.

awesome! thanks you!

@protich, if you should need any help releasing a new version, and I could be of assistance, please consider involving me. I too have considered a fork of the project in order to manage merging of bug fixes and other small features needed for Cleco's transmission operations department.

Good news! Thanks, @protich
But, can we please get the list of features that would be included in osTicket 1.11? Thank you.

And how is going releasing today ? :) I still refresh page waiting for stable 1.10 :)

We'll be doing last minute merging today then QA before we cut the release. I'll post an update here.

Any news about release?

The tip of develop branch is close to the final version pending any last minute bug fixes from our testers and a security vulnerability fix we'll publish right before the release.

Anyone willing to do quick upgrade test using a copy of your production environment?

I have a couple of envronments, including one productions. Happy to test.

When I pull from the tip of develop, it says that I am installing "1.8-git"... is this correct?

@protich i'd be happy to.

My plan is to do a fresh install of OSTicket because our current system has gotten buggy overtime since 1.6. we're looking forward to this update!

@themunchkinman -- that's correct.

Issues To Address

• [ ] Crash on 1.8.x upgrade due to php7 changes

Tested a clean install, went well (I'm avoiding PHP 7 though, still on 5.5/5.6).
If I'm running 1.10-RC3, do I need to do an upgrade? I am about to go over the top of one of my production setups...

No really torture test, but so far no breaks with normal operation...
Several manual fixes that I had done seem to be present in this version of files...

@themunchkinman - care to elaborate on the manual fixes you speak of?

I'm running the new version for the last 6 hours and we can only identified one issue.
When doing a response on a ticket there is no "Wait" overlay like when creating a ticket, this as create some doble entry form some tech that clicked twice on the "Response" button, but out of that look fine for us.

after a short testing, i found some issues (upgrade from 1.9.12 to 1.9.14 and then to develop)

• after the upgrade, the custom forms arent linked anymore.
• when editing a ticket an letting a date field empty, there is an error (date setting: standard, language german)
• under the "my tickets" link, there are not only "my ticket" but also the team tickets. that will confuse the agents after the upgrade.
  i think i will find more issues. i ll go ahead with testing.

@JediKev - there were a few php edits that I did, mostly fixing the knowledgebase/FAQ, which appears to be incorporated, along with some semantics. I also did some manual edits to the SQL database from the fresh setup with RC3. It created some tables with certain fields flagged as primary key/unique that had caused some warnings because some of the tables are just a register of relationships and thus are often non-unique and not necessarily keyed.

@markus4000

Also, it has been my experience since 1.10 began that certain anomalies would occur when moving from 1.9.x, and other previous versions. Because of that, I've been planning to find a stopping point for the transition, and to work it in phased, archiving the old instance and database, and start clean with the new. I've done multiple tests of copies/backups of my in-service 1.9.x instance and could never get it to go through completely clean.

I'm checking on the date field info to see if I get the same issue on my clean build.

if I'm not mistaken, "My Tickets" was designed in include those assigned to a team to which you are a member...

BTW... to everyone here... I'm so happy to see this project still alive and the community support. I've been using osTicket since 2008 and still haven't found anything that does exaclty what I want the way osTicket does.

Is the stable version released? Can't find it..

@mrdanne if you can't find it here: osticket.com/download
then it hasn't been released yet. As @protich posted 19 hours ago there is an updgrade issue that needs to be dealt with prior to release.

I can't wait until the new release! Been looking forward to it for a long time. 😄

while upgrading, I had the unique key error with the osr_ticket_event table
too. so i manually removed the primary key and AI from the "unique" field
before upgrading. that helped.

Am 26.10.2016 05:57 schrieb "TheMunchkinman" [email protected]:

@markus4000 https://github.com/markus4000

Also, it has been my experience since 1.10 began that certain anomalies
would occur when moving from 1.9.x, and other previous versions. Because of
that, I've been planning to find a stopping point for the transition, and
to work it in phased, archiving the old instance and database, and start
clean with the new. I've done multiple tests of copies/backups of my
in-service 1.9.x instance and could never get it to go through completely
clean.

I'm checking on the date field info to see if I get the same issue on my
clean build.

if I'm not mistaken, "My Tickets" was designed in include those assigned
to a team to which you are a member...

BTW... to everyone here... I'm so happy to see this project still alive
and the community support. I've been using osTicket since 2008 and still
haven't found anything that does exaclty what I want the way osTicket does.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/osTicket/osTicket/issues/3399#issuecomment-256243511,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEMAZoAW5gVrz0JjyGie_qa0AaiFMc6tks5q3s-ugaJpZM4KXR2e
.

@tomlaf - Pull request #3426 addresses the overlay issue.

@markus4000 - can you clarify more on ticket_event issue? Also you mentioned custom forms getting dropped - what object were the forms attached to?

@protich : The primary key issue was my fault. sorry. I found out that somehow there was a field "unique" but this is not part of the osticket standard installation.

@markus4000 - Thank you so much for clarifying, I was going nuts trying to trace the issue. You had mentioned custom forms getting dropped -- care to elaborate? What version were you upgrading from?

Just to clarify the unique/primary key issues in the DB that I kept running into was on the table for associating agents with teams. I had done a fresh install of RC3 and when it built out the database the first field was set as primary and unique, and thus for every additional agent I would add to a team, I would get a database error for duplicate value, but it would at least process. I resolved it by removing the primary key and unique flags from the field in MySQL.

[INSERT INTO ost_team_member SET team_id = '4', flags = 1]
Duplicate entry '4-0' for key 'PRIMARY'

Here is an additional database error I have received as well. This is done when adding an item to the ticket status list.

[UPDATE ost_ticket_status SET extra = 'susp' WHERE ost_ticket_status.id = 6 LIMIT 1] Unknown column 'extra' in 'field list'

@protich : I upgraded from 1.9.8 to 9 to 11 to 12 to 13 to 14 then I compared the whole database with a clean 14 Installation, to make sure that I have a proper 14 before I upgrade. Thats how I found my fault.

But I also found out that in the table "ost_ticket" the field "flags" was missing before updating from 1.9.14 to 1.10dev

• [ ] Custom Forms: I have 20 helptopic and each has its own form "x". After update, all the helptopics lost the connection to the form. so I have to go to: admin panel -> manage -> help topic -> update help topic -> forms: and there I add manual the custom form that was linked before.
  It does not loose the form it self. it does just loose the connection between helptopic and the form.
• [x] Solved in 1.10; Date Issue: when I edit a ticket that has a custom form with several date fields (optional), I leave them empty and I save; the Warning: _Warning: date() expects parameter 2 to be long, string given in /home/httpd/vhosts/regipedia.ch/ticketpreview.regipedia.ch/include/class.forms.php on line 1769_ appears. The warning appears too, if I open new ticket from the client view.

• [ ] Task: printing is not working
• [ ] Task: after creating a new Task, it is not possible to create another task without going to another page before pressing "new task"
• [ ] Task: it would be good if on new task creation the home department would be selected by default.
• [ ] Task: cant edit duedate once task is created
• [ ] Task: Email Templates %{Task.ticket_link} and %{task.due_date. . . .} cause a error. and maybe others too.

Can you make from v1.10 new branch?

Also - when will be languages compiled?

@wacki4
Q: Can you make from v1.10 new branch?
A: You could... but generally speaking you should use the official release at osticket.com/download.

Q: Also - when will be languages compiled?
A: I was told late last week that they should be compiled soon (days).

But if i want to use git, to make some improvments for myself best way
would be clone 1.10 branch, not develop. This is why i'm asking about it,
it was made for previous versions.

7 lis 2016 6:04 PM "ntozier" [email protected] napisał(a):

@wacki4 https://github.com/wacki4
Q: Can you make from v1.10 new branch?
A: You could... but generally speaking you should use the official release
at osticket.com/download.

Q: Also - when will be languages compiled?
A: I was told late last week that they should be compiled soon (days).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/osTicket/osTicket/issues/3399#issuecomment-258895561,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAp6epJOCK3xWWzSey9SEXPNPhhPwKHgks5q71oggaJpZM4KXR2e
.

@protich Is the progress of osTicket dead again?

Just asking... Thanks.

Keep an eye on the github milestones tab within the coming weeks... We'll be assigning issues to 1.11, should give everyone a better idea of release schedules. This thread has done it's job

@rbukovansky No.

Why new Language Packs are not yet compiled?

It feels like the project is dead again. there are still many bugs in 1.10 but no activity from the devs. And the translations arent available too. I think since @greezybacon doesnt participate anymore the soul of the project has gone.

Major improvements are coming. Meanwhile, github isn't really the place to discuss the soul... the forums and freenode are better for that.