Family Historian User Group

CP will have a list of things they are aiming to achieve by the next major update and much of their time will be spent working on this. They'll also have to spend time fixing errors that are reported that they consider to be important enough to warrant going into an update. I expect they also occasionally add some enhancements if they think it is a good idea and it isn't going to take very long to do and isn't likely to break anything. The italics issue isn't an error (I assume it is working as designed) but is probably a larger piece of work so they will add that to their 'possible future enhancements' pile. I had one major wish-list request which I had to wait 15 years to appear (rich text) and got very frustrated by all the other features that were considered higher priority than this (projects, maps, more diagram types, etc.). However, I did also understand that not everyone has the same priorities. I know they probably planned to add rich-text much earlier but priorities change, timescales lengthen, etc.

I do agree that it would be good if they had an alternative message for when a ticket is closed because they're added it to their 'possible future enhancement' list so that the user understands the reason for closing.

Looks like we've landed on a simple enhancement if CP are minded to implement it - clarify that closing the ticket does not mean that the issue is no longer under consideration.

Out of interest, I trawled through my bug reports made between this time last year and October (so time to implement in a recent update):

"Will be fixed in next update" - 5 (including 2 invitations to test in preview)
"Referred to developers" - 3 now fixed, 5 still pending (they are all definite bugs rather than just a difference of design opinion, but none corrupt user data)
"Thank you for your feedback" - 1 (that is CP language for "we don't agree, but don't want to discuss )
Disappeared without trace - 1 (deleted from system?)

I don't have anything else to directly compare it with, but that feels like a reasonable performance.

Incidentally, it would be useful to be able to see an overview of all the tickets you have raised, but that is probably a much bigger change than simply changing a default message.

I'll.... open a ticket! unless somebody else wants to do it.

Mark1834 wrote: ↑

06 Dec 2022 16:43

Looks like we've landed on a simple enhancement if CP are minded to implement it - clarify that closing the ticket does not mean that the issue is no longer under consideration.
...

I'd agree with that. Should help the customers to understand what's going on.