When tagging an invoice into a project I like very much the feature where it brings on a list with all projects having that string on characters that were typed. That way the system prevents you creating another project for the same job (different by a character/ space, whatever, so it helps you bringing everything in one project).
However I thought this list includes all projects having that character, but I noticed today that it does not.
That means actually the list is not comprehensive, therefore with or without list… there is not much difference. There is a high risk of creating another project with a similar tag, therefore invoices pertaining to the same project landing into different projects and therefore not showing full picture.
Could you please look at producing the entire list of those projects when tagging an invoice/ purchase? As the list (so the feature) is already there, I figure this should be an easy fix - needs just to make sure the list is comprehensive (maybe/ hopefully just a search field adjustment?)
I’m sure this will cap the result set to maybe 10 entries. If you had say 200 projects all starting with “sa” it wouldn’t be practical to show them all on a huge drop down.
It is correct that for one or two characters the list may be very long and potentially impracticable - however if you put a certain string of 3 - 6 characters the list should reduce significantly.
E.g. if I would put “callout”, it should bring all projects having “callout” in the name, I would have thought. This would be to enable user not to create another project for the same job, different by maybe just one space/ character (or more) - but then makes it difficult to follow.
So, while putting one character would give the whole list, the more unique you put the string of characters, the shorter the list. Then it would be down to the user to ensure the characters used reduce the list to a meaningful number.
I have noticed that in some occasions I did not have a number of 10 entries and the project I was looking for (existing) was still not there.
I believe having the predictive search is a really good feature, but it is misleading if not all the projects are there - as it leaves room for confusion.
I hope this clarifies - sorry if I am still not very clear…
I don’t think the predictive search should extend to cover every possible instance, that’s generally not how predictive searching works. People will use all different types of naming conventions for project tags
dept-x-proj-1
dept-x-proj-2
dept-x-proj-3
etc
Even keying in 5 characters may not guarantee the list will be that short and having 100s of results on a predictive search menu is not going to be practical and will be slow to retrieve.
Just to go back to the original problem, you need a way to avoid keying in a project name that is already in use, when your intention is to create a new project definition? If that’s the case I would think a better solution would be to colour code the tags. Maybe highlight it green if it is already in use.
