nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Moderators should Populate the Known Product Issues Category with Confirmed Bugs

markus1957

For all practical purposes the Category at issue is not being maintained. Either use it or delete it. IMO it would be a valuable resource and also demonstrate to users that Quicken is interested in product improvement when Issues are listed as Resolved. Currently, based on the activity in this category, a user could conclude either Quicken has no bugs or Quicken developers are not very interested in product improvement.

Find more posts tagged with

Implemented

Status: Implemented

Comments

smayer97

Agreed.... This was ALL LOST during migration.... (along with other dual category threads).

In GetSat, the "Known Product Issues" category was a complementary and secondary category but since Vanilla only allows ONE category and TAGS are not currently active, there is no way to preserve the original category also.

smayer97

+1 (still cannot add votes - javascript permission error).

thecreator

Hi @smayer97 ,

I am using Firefox 52.9 and Java 8 Update 201 is installed..
I clicked the down arrow which increased the Vote.

Greg_the_Geek

thecreator said:

Hi @smayer97 ,

I am using Firefox 52.9 and Java 8 Update 201 is installed..
I clicked the down arrow which increased the Vote.

FWIW, Java and JavaScript are two different languages.