View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Support us on Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - Tickets automatically change status to "IDLE" when saved. (SOLVED) - ProjeQtOr
 

Tickets automatically change status to "IDLE" when saved. (SOLVED)

More
15 Dec 2024 23:25 #1 by mvrka4
Hello and good morning. I have been having an issue that is likely something simple I have done...but don't know exactly how I did it or why it would have the effect it does.

I was testing the ticking capabilities and how the workflow runs. When... I went to change the information in the ticket, the boxes were all grayed out. i.e. locked fields.

I tried a few different things to find out why this was happening....the only thing I have discovered is that when I save the ticket....it changes it in the database to IDLE "1" from "0".
Tried it with old test tickets as well as newly imputed tickets. Doesn't matter how I configure the treatments, or don't for that matter. As soon as I SAVE the ticket, everything is grayed out and the database switch is set to IDLE "1".

Doesn't matter the project, type or activity, when saved it changes to IDLE "1" in the database. Using MySQL

If there is more information you need, please let me know.
 

Please Log in or Create an account to join the conversation.

More
16 Dec 2024 10:15 #2 by Arkhanje
Hello

We're going to need a little more information so that we can give you the beginning of an answer.
There are about forty fields on the tickets...
Which ones are read-only?
What profile do you have?
What are your rights on the tickets?
Have you set delays on tickets?
Is the "recorded" status a status that triggers the "in progress" macro status?
Take a screenshot of these elements so that we can give you a clue!

Please Log in or Create an account to join the conversation.

More
18 Dec 2024 07:14 #3 by mvrka4
Well... TBH, it was an ID10T error. The primary culprit was me.

10 Cent Story: I switched some flags much, much early in my testing of the software. When I really didn't completely understand what I was doing.

Five Dollar Book:
After many hours... I installed a separate install, recreated my test info there, trying to recreate the issue there. Which was after I noticed that there was an ID number skip from 11 to 31.... I figured I need to at least recreate the tickets up to 13....... .......

Turns out no issues on the other test instance.......so I was hmm........okay I'll update the software to most current (I was only 2 minors versions off). Maybe, there was a big change in a small version.....

After all that....maybe 8 hours to be embarrassingly frank.....

I was killing me.....I couldn't sleep. The steps I took were running through my head like sheep. Mouse click sounds instead of the bleats of sheep.

I had created a couple of ticket types earlier, some other the switches I switched were "lock and change by status only" or something to that effect.......

And of course I copied these settings over to a few other ticket types which were also locking the information and only changing on status.

(I DID learn how to lock an item through the database to prevent it from being edited.... )

Now, tho, everything is working as fine as I think it should be. Unfortunately, I will not discover any other errors until I get more information in and catch it error visually much later.
So far it seems to do all it says it can do "on the box" so to speak.

A few things things....
1. the "logfile" leaves a lot to be desired.... (although I may not have found the "good" logfile yet i.e. more info then just database stuff)
2.Intergration/ communication with ZenCart. they both use the same archetecture....That would be an awesome mod tbh.
3. Email and PDF format (s) to change, edit, colors, add information etc...

I didnt realize I could upload images as a new user on the forum....but now I know. And if I do have any issues in the future I will definetly provide alll the information you ask as a reference. I was kinda in a sad panic....the ticketing and planning was the most looked for functions...and was just throwing out a life preserver.

And of course, thank you for your prompt reply, patience and questions.
So far this software solves issues we were having, so we plan to be around a while and have some ideas of our own to impliment for some added functionality.

 
The following user(s) said Thank You: Arkhanje

Please Log in or Create an account to join the conversation.

More
18 Dec 2024 09:11 #4 by Plucks
Hi,
Oh, my. Thanks for that story !

Please Log in or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.035 seconds

Cookies settings

×

Functional Cookies

Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.

Session

Please login to see yours activities!

Other cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.