Drop Origin Selector From Issues

The Future of Issue Tracking: Why We're Dropping the Origin Selector

As we continue to evolve and improve our issue tracking system, we're making a significant change that will impact how we view and interact with issues. In this article, we'll explore the reasoning behind dropping the origin selector and what this means for our community.

The Current State of Issue Tracking

Currently, our issue tracking system displays issues from different origins, such as Maestro and Red Hat. While this provides a comprehensive view of all issues, it can also be overwhelming and make it difficult to focus on specific problems. The origin selector was introduced to help users filter issues by their source, but it has limitations.

The Problem with the Origin Selector

The origin selector only allows users to view issues from a single origin at a time. This means that users have to constantly switch between different origins to get a complete picture of the issues. This can be frustrating and time-consuming, especially for users who need to track multiple issues from different sources.

The Benefits of a Column-Based Approach

To address these limitations, we're proposing a column-based approach to issue tracking. Instead of displaying issues from different origins in a single list, we'll display them in separate columns. This will allow users to view issues from multiple origins simultaneously, making it easier to track and manage issues.

Why a Column-Based Approach is Better

A column-based approach offers several benefits over the current origin selector system. Here are a few reasons why we think this approach is better:

• Improved visibility: With a column-based approach, users can view issues from multiple origins at the same time, making it easier to track and manage issues.
• Reduced switching: Users won't have to constantly switch between different origins to get a complete picture of the issues.
• Enhanced collaboration: A column-based approach makes it easier for users to collaborate and work together on issues, as they can view and interact with issues from multiple origins simultaneously.

What's Next

Once we've implemented the column-based approach, we'll be working on adding filters to help users narrow down their view of issues. This will include features like filtering by origin, as well as other criteria such as issue type and priority. With these filters in place, users will be able to quickly and easily find the issues they need to focus on.

The Road Ahead

Dropping the origin selector and implementing a column-based approach is just the first step in our efforts to improve issue tracking. We're committed to continually evolving and improving our system to meet the needs of our community. We're excited to hear your feedback and suggestions on how we can make issue tracking even better.

Conclusion

Dropping the origin selector and implementing a column-based approach is a significant change that will impact how we view and interact with issues. While it may take some time to adjust to this new way of tracking issues, we're confident that it will provide a more streamlined and efficient experience for our community. We're excited to see how this change will benefit our users and look forward to continuing to evolve and improve our issue tracking system.

Frequently Asked Questions

• Q: Why are you dropping the origin selector? A: We're dropping the origin selector because it has limitations that make it difficult for users to track and manage issues.
• Q: What's the benefit of a column-based approach? A: A column-based approach provides improved visibility, reduced switching, and enhanced collaboration.
• Q: When will the column-based approach be implemented? A: We're working on implementing the column-based approach now, and we'll provide updates on our progress.
• Q: What's next after the column-based approach is implemented? A: We'll be working on adding filters to help users narrow down their view of issues, including features like filtering by origin.
  Frequently Asked Questions: Drop Origin Selector from Issues

As we continue to evolve and improve our issue tracking system, we've received many questions about the decision to drop the origin selector and implement a column-based approach. In this article, we'll address some of the most frequently asked questions and provide more information about this change.

Q: Why are you dropping the origin selector?

A: We're dropping the origin selector because it has limitations that make it difficult for users to track and manage issues. The origin selector only allows users to view issues from a single origin at a time, which can be frustrating and time-consuming. By implementing a column-based approach, users will be able to view issues from multiple origins simultaneously, making it easier to track and manage issues.

Q: What's the benefit of a column-based approach?

A: A column-based approach provides improved visibility, reduced switching, and enhanced collaboration. With a column-based approach, users can view issues from multiple origins at the same time, making it easier to track and manage issues. This approach also reduces the need to constantly switch between different origins, making it more efficient and streamlined.

Q: How will the column-based approach work?

A: The column-based approach will display issues from different origins in separate columns. This will allow users to view issues from multiple origins simultaneously, making it easier to track and manage issues. We'll also be working on adding filters to help users narrow down their view of issues, including features like filtering by origin.

Q: Will I still be able to view issues from a single origin?

A: Yes, users will still be able to view issues from a single origin. The column-based approach will provide an additional way to view issues, but users will still have the option to view issues from a single origin if they prefer.

Q: How will the column-based approach affect collaboration?

A: The column-based approach will enhance collaboration by allowing users to view and interact with issues from multiple origins simultaneously. This will make it easier for teams to work together on issues and will improve communication and collaboration.

Q: What's next after the column-based approach is implemented?

A: After the column-based approach is implemented, we'll be working on adding filters to help users narrow down their view of issues. This will include features like filtering by origin, as well as other criteria such as issue type and priority. We'll also be continuing to evolve and improve our issue tracking system to meet the needs of our community.

Q: Will the column-based approach be available for all users?

A: Yes, the column-based approach will be available for all users. We're committed to providing a consistent and high-quality experience for all users, and we'll be working to ensure that the column-based approach is available for all users.

Q: Can I provide feedback on the column-based approach?

A: Yes, we encourage users to provide feedback on the column-based approach. We're committed to continually evolving and improving our issue tracking system, and we value the input and feedback of our users. Please don't hesitate to reach out to us with any questions, comments, or suggestions.

Q: When will the column-based approach be implemented?

A: We're working on implementing the column-based approach now, and we'll provide updates on our progress. We're excited to bring this new feature to our users and look forward to hearing your feedback.

Q: Will the column-based approach affect the way I track and manage issues?

A: Yes, the column-based approach will affect the way you track and manage issues. However, we're committed to providing a seamless and efficient experience for our users. We'll be providing training and support to help users get the most out of the column-based approach.

Q: Can I customize the column-based approach to meet my needs?

A: Yes, we'll be providing options for users to customize the column-based approach to meet their needs. This will include features like customizing the columns and filters, as well as other options to help users get the most out of the column-based approach.

Conclusion

We hope this Q&A article has provided more information about the decision to drop the origin selector and implement a column-based approach. We're committed to continually evolving and improving our issue tracking system, and we value the input and feedback of our users. If you have any questions or comments, please don't hesitate to reach out to us.