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

Mismatched Logout Button Color in Organization and Event Dashboards #1421

Closed
akhilender-bongirwar opened this issue Jan 12, 2024 · 2 comments
Labels
bug Something isn't working unapproved

Comments

@akhilender-bongirwar
Copy link
Contributor

Describe the bug
The logout button's color needs to be changed to red in both the organization dashboard page and the event dashboard, matching the color scheme present in the superadmin screen.

To Reproduce
Steps to reproduce the behavior:

  1. Navigate to any organization dashboard
  2. Check the color of the logout button
  3. Navigate to Event Dashboard
  4. Check the color of logout button

Expected behavior
The logout button color should be consistent and set to red, matching the appearance in the superadmin screen.

Actual behavior
The logout button is not red in color on the organization dashboard and event dashboard screens.

Screenshots

  • Organization Dashboard Screen
    logout1
  • Event Dashboard Screen
    logout2

Additional details
The expected color of the logout button should match the appearance in the superadmin screen.
logout0

Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359

@akhilender-bongirwar akhilender-bongirwar added the bug Something isn't working label Jan 12, 2024
@akhilender-bongirwar
Copy link
Contributor Author

This is a good first issue, anyone can take it : )

@Cioppolo14
Copy link

Thank you for your submission. We are now focusing on three types of issues as priority areas:

  1. The improvement in the reliability of our code base. There are many issues created to test existing code. It is a good place to start if you want to understand the operation of various apps. When you submit PRs, we automatically check to see whether the code you submitted has been covered by testing and that each file meets the minimum standard level of the repository as a whole. You won’t be able to avoid understanding testing regimes to contribute to Talawa.
  2. The fixing of bugs and features that seriously hamper the user from using the application. The apps have various shortcomings. The most obvious ones are where the apps do not work as expected. For example buttons that don’t work, errors or messages that are not displayed to make the user understand what to do and many more. Think of any difficulty you have had in getting things working, there could be a bug there waiting for you.
  3. Coding of screens for issues created by our Contributor team based on our soon to be updated design guide. This may include updates to existing screens. @rishav-jha-mech is leading this process for the Talawa Admin project
  4. The creation of additional or updated documentation that helps with improving both the experience of the end user and the various GitHub contributors who support the development of our software. This would include user guides.

We will only be accepting feature issues for deficiencies that are obviously lacking in the apps. These are things that make it very difficult to operate the apps. Even so, the PRs will still require you to understand testing as stated before.

Closing

@Cioppolo14 Cioppolo14 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unapproved
Projects
None yet
Development

No branches or pull requests

2 participants