New Screen to track the Status of Reported bugs found on Scriptcase

Scriptcase 8 Suggestions
#1

The suggestion is for Scriptcase to create a screen where the status of the bugs reported displays the date the bug was reported, the date the bug was analyzed and either was approved to be worked on or rejected with a reason for the rejection, a date for when the bug is expected to be corrected would be nice too.

The reason for this suggestion: Scriptcase just started new free “classes or webinars” I think on Fridays, I am not sure why but I would think Scriptcase should be more worried about addressing real bugs and helping customers instead of ignoring actual real bugs that hold us back in development.

Currently there is no way to track where the status of a submitted bug is at any point in time.

I have submitted a couple of bugs, one is a real problem with multiple fields on the search, it has been close to a month not sure but nothing has been done about this and I am not if it is even being looked at. Here is the link for the first one: http://www.scriptcase.net/forum/showthread.php?5617-Multi-Search-on-Grid-does-not-work&highlight=javierx1

Today I am running a simple search with a date and when I run it empty it returns all the records as expected but as soon as I select a set of records I have to start over, even when I hit the “cleanup” button the search is still returns the last selected set of records, it is a simple search nothing special and I am not sure when I can even expect for someone to look at it.

#2

Maybe they should start using Mantis Bug Tracker.

#3

I would also like to see all previous versions available as downloads. Sometimes sc gets a bugfix and promptly gets new bugs with it as well. It’d be nice to be able to download an older sc version as well.

#4

They are using Mantis internally, but all Portuguese… I agree though that communication should be more open and clear. Far better than ‘issue reported to bugsteam’.

#5

Hmm, I see.

#6

I can only say the Portuguez, Japanese, Chinese it makes no difference, the screen should just have the bug status, the title, the date entered, the date expected to get fixed and the actual date of release. Once the bug is fixed the status should be closed and the Scriptcase update would prove the fix is done or not. The language is not that important a date is a date and a status we can translate maybe si?

#7

I offered once to keep track of that and Mantis is already running on our website. But so far no sigar. It’s more than just Mantis. It requires that bugs are better documented, not only by SC but also by the reporter.

#8

I don’t know what Mantis does or how it works however as you can tell I have seen no interest from anyone is Scritpcase so is not even been considered so my guess things will continue to be as they are now, going into a “dark hole” and staying there. Thanks for the response.

#9

Mantis is a bugtracker. If it would be accessible by us it would mean that we could track the issues being solved but also prevent double postings. I think it would increase quality a lot, but to SC it would mean that they would have to maintain two bugtrackers. As some devs are Portuguese only it simply is a language barier. I don’t like the ‘reported to…’ message. Trying hard to get a better communication regarding these.

#10

“Reported to…” simply equates to “sent to dark hole, adios amigos.”

I can only suggest the bug tracker be implemented and shared with a link to “Google Translate” so we can simply cut and paste what we need translation of, google translate is not is not always accurate but better than nothing.

#11

I suggest to use FossilSCM - just as page for bug tracking. We can create new tickets there, and Netmake can “set as repaired” with short developer’s explanation. Please check: http://www.fosill-scm.org. (Or great Timeline finctiionality: http://www.fossil-scm.org/index.html/timeline?y=ci ) I am using Fossil few years and its great not just as control version system,but also as page to contact with my Clients.

Guys, let’s create it. Forum is ok but we can’t track reported bug. What do you think about?

daretzki

#12

Hello Daretzki,

We do already have a bug tracker and version control system, but they are not open for public. Sometimes we discuss on having it open publicly but we haven’t decided anything on that matter yet.

Thanks,
Bernhard Bernsmann

#13

[QUOTE=bartho;25884]Hello Daretzki,

We do already have a bug tracker and version control system, but they are not open for public. Sometimes we discuss on having it open publicly but we haven’t decided anything on that matter yet.

Thanks,
Bernhard Bernsmann[/QUOTE]

Five months on…

@bartho, any news on this?

@others - please keep this thread alive.