Search found 5 matches

by Peter
Fri Sep 14, 2007 6:59 am
Forum: Gold Support (Dragnet) -- Read-only
Topic: status value and status type mismatch in "My Open Items
Replies: 3
Views: 26349

Just a note on what was happening earlier ;
I think the "problem" was caused due to the item (specifically the resolver field) was changed to different people during testing. That's why the item was shown one time, and not shown the other time.
by Peter
Fri Jun 22, 2007 5:34 am
Forum: Support (Fortress)
Topic: How to remove "old" Dragnet data out of Fortress D
Replies: 1
Views: 4453

How to remove "old" Dragnet data out of Fortress D

Our IT-Service department has updated Vault and Dragnet to Fortress, we have asked them to uninstall Dragnet first, so the Dragnet Database could be removed also, but they didn't do this. So the "old" Dragnet database with all data is converted to the "new" Fortress database. Is ...
by Peter
Fri May 04, 2007 7:20 am
Forum: Gold Support (Dragnet) -- Read-only
Topic: status value and status type mismatch in "My Open Items
Replies: 3
Views: 26349

Sorry, :(
We can't reproduce the problem, its seems to be working correct now!
by Peter
Wed May 02, 2007 7:30 am
Forum: Gold Support (Dragnet) -- Read-only
Topic: status value and status type mismatch in "My Open Items
Replies: 3
Views: 26349

status value and status type mismatch in "My Open Items

In the "My Open Items" in the OPEN section (tab) we can see all items with the status type OPEN, so when we make a new status value TEST with status type OPEN (in Database option menu), we will see also the item with the status value TEST. When we go to the COMPLETED section (tab) we only ...
by Peter
Wed May 02, 2007 7:17 am
Forum: Support (Dragnet)
Topic: Deleting 'unconfirmed' status mislabels Open/My Open tabs
Replies: 3
Views: 28191

Deleting the unconfirmed status no longer messes up the open

In the release notes of version Dragnet 1.0.5 stands that this bugs is fixed:
-> Deleting the unconfirmed status no longer messes up the open and my open tabbed display.

But we use version 1.0.7 and the bug still exists!

:?: