* Unscheduled * Issues
What determines an "unscheduled" issue and why on several of my project "home pages" do I have * Unscheduled * listed multiple times? One projects displays it 3 times, another 6, another 4.
I created a new project and used another as a template, haven't added a single issue yet, and voila, I have * Unscheduled * issues listed 4 times, complete with the "number of issues" linked to nothing.
What is this and how do I get rid of it?
All of our issues are assigned and given start/due dates. (of course, putting in the start/due date isn't always an option depending on how you create an issue...maybe another fix for the new version?)
englea
· 1 |
|
Friday, December 19, 2008, 2:48:50 PM |
0
|
Which version of Gemini are you running? If 3.0.4, please download the zip file and re-run the stored procedures script. |
||||
|
0
|
3.0.4. Which .zip file? The database one? For the record, 3.0.4 is the only version we've used so it's not an upgrade issue. thx |
||||
|
0
|
Download the whole 3.0.4 zip: http://countersoft.com/downloads/csfiles/CounterSoftGeminiv304.zip and run the create_procs.sql script. We have issued a fix for 3.0.4 in the SQL script. |
||||
|
0
|
I noticed that 3.1 is out of beta so I'm upgrading. If the upgrade doesn't fly, I'll download the zip and run the script. |
||||
|
0
|
Please make sure that your license has not expired before upgrading. |
||||
|
0
|
We're good. *Unscheduled Issues * gone. |
||||
|
0
|
Thanks for the update. |
||||
|
0
|
Ok. Un scheduled issues are back after 1 week of using the new version. We just changed over to a new app version (here, not Gemini) and now there are 4 unscheduled tasks under the new version number where only TWO new tasks have been added. Definitely a bug in there somewhere.
Suggestions? |
||||
|
0
|
Did you restore your database? Please make sure that you have run create procs.sql |
||||
|
0
|
Is it a requirement to run that every day? We just upgraded. New version, new procedures (that we were told would fix this), etc. It's a bug. Bugs = bad mojo. re-read previous posts above. thx. :)
|
||||
|
0
|
I know you have upgraded, but did you run create procs when doing the upgrade? |
||||
|
0
|
yep. All 3 as instructed on page 10 of the installation guide. is there a different one? |
||||
|
0
|
That is ok, its just that I fail to see how it sorted the problem and then it came back. so thought you might have restored your database.... Is it possible to send a zipped backep of your database to support? |
||||
|
0
|
i can do that. Here's what I "think" may be the problem, but then again I could just be throwing loose change into a fountain. We published versions of an application just about every other day as we make minor upgrades (rapid app development) and I'm wondering if the "unscheduled" items are leftover "unclosed" tickets that have no real deadline. where do I send the database? |
||||
|
0
|
I don't think this is the issue, but will try it to make sure. Please send to support at countersoft dot com |
||||
|
0
|
I found the problem, and it is just as I suspected. Apparently when you select "<None>" for "Fixed for version" or if the issue is outstanding (open) and tied to a version that has been marked "Released", you'll suddenly end up with "Unscheduled Issues" on your application. It's not the database. It's the application. And it's not necessarily a bug, just a matter of how the application marks things read from the database. I have three issues open that are future version features not tied to a current or past version, and not tied to "Fixed for version". When I changed the "Fixed for Version" to a generic version we have, all the unscheduled issues started going away one by one. Savvy?
|
||||
|
0
|
Sorry, but look like I've missed somehting here. Are you talking about the issues list page or the project home page? |
||||
|
0
|
Project home page. Where you have links for road map, change log, reports, etc. Lists components on the left, VERSIONS in the middle, and Resources to the right of that. VERSIONS is where the unscheduled issues appear. Well, appeared anyway. Like I mentioned above I assigned a "Fixed for Version" version number to all the "unscheduled" issues and they disappeared. |
||||
|
0
|
I see, so as you've said earlier this is not a bug. This is the way Gemini works, if an issue does not have a "fixed in version" associated with it then it will be marked as unscheduled. |
||||
|
0
|
Right-o. Maybe we have two different definitions of "Unscheduled". Unsheduled means, to me, quite literally "not scheduled", or a "bug" as in unanticipated. I'm not sure why it's tied to "Fixed for Version" instead of "Affected Versions" or the schedule, but alas, issue resolved with a work around. Still a great app regardless. |
||||
|
0
|
Our definition of "Unscheduled" is issues that do not have a version for which they will be fixd (fixed in version is none). I think you take it as status. Thanks for the good feedback, much appreciated. |
||||
|
0
|
[quote user="englea"] Right-o. Maybe we have two different definitions of "Unscheduled". Unsheduled means, to me, quite literally "not scheduled", or a "bug" as in unanticipated. I'm not sure why it's tied to "Fixed for Version" instead of "Affected Versions" or the schedule, but alas, issue resolved with a work around.[/quote] I have to agree with englea here - surely it is more use to track bugs via the version they affect, not the version they are fixed in. I would expect a dashboard/summary page to show outstanding bugs and things to do. Once the bug is fixed, it doesn't seem neccessary to display it so prominently. |
||||
|