Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend "Make visible in stats?" toggle in Categories, Moods, and Strategies editor #2142

Closed
julianguyen opened this issue Oct 5, 2022 · 1 comment · Fixed by #2168
Closed

Comments

@julianguyen
Copy link
Member

julianguyen commented Oct 5, 2022

Description

The "Make visible in stats?" toggle in the Categories, Moods, and Strategies editor hides these posts from being displayed on a user's profile page.

image

Let's extend this toggle so that it prevents the user from being able to tag these Categories, Moods, and Strategies in other places.

  • Categories can be tagged in Moments and Strategies
  • Moods and tagged in Moments
  • Strategies can be tagged in Moments

This will not remove existing tags, but rather prevent the user from adding tags to new posts. This feature will be helpful if a user does not want to see these posts.

Acceptance Criteria

  • When the visible value is true, in addition to hiding it in profile stats, hide it from being able to tag it (in the areas listed above)
  • Change the label "Make visible in stats?" to "Make visible to tag and display in profile stats?" (Please use Google Translate to update the translations, it will be reviewed for accuracy later)
  • In the Story component, update the visual indicator ("Visible in stats") to show the following icon with the tooltip label, "Not visible to tag and display in profile stats" (Please use Google Translate to update the translations, it will be reviewed for accuracy later) WHEN the visible value is false
    image

Please assign yourself (via the Assignees dropdown), if you do want to work on this issue. Can't find yourself? You need to join our organization.

Check out our Picking Up Issues guide if you haven't already!

@julianguyen
Copy link
Member Author

I'm unassigning you @yasirazgar cause you're already assigned to an issue. We have a general rule to be assigned to one issue at a time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants