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

Metadata issues #3986

Closed
matthewelwell opened this issue May 20, 2024 · 0 comments · Fixed by #4069
Closed

Metadata issues #3986

matthewelwell opened this issue May 20, 2024 · 0 comments · Fixed by #4069
Assignees

Comments

@matthewelwell
Copy link
Contributor

  1. This Tooltip doesn't make any sense to me. I don't think it's necessary as we have the description and link to the docs below.
image
  1. I'm not sure what these null values are. Maybe this is old data.
image

The JSON responses are as follows:

// GET /metadata/fields/

        {
            "id": 1,
            "name": "JIRA Ticket Number",
            "type": "str",
            "description": "",
            "organisation": 18
        }
// GET organisations/:id/metadata-model-fields/
        {
            "id": 1,
            "field": 1,
            "content_type": 39,
            "is_required_for": []
        },
        {
            "id": 2,
            "field": 1,
            "content_type": 55,
            "is_required_for": []
        }
  1. Requeried -> Required
Screenshot 2024-05-20 at 17 27 58
  1. Be more descriptive in locations where metadata should be shown, guiding users to where they can configure the metadata.

image (3)

@Flagsmith Flagsmith deleted a comment from flagsmith bot May 20, 2024
@Flagsmith Flagsmith deleted a comment from flagsmith bot May 20, 2024
@novakzaballa novakzaballa linked a pull request May 31, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants