Let's add "master" and "develop" tags to issues?

[Xyntexx]

Let's add master and develop tags to issues? Then developers could use the develop tag when issue is found in the develop branch? Then it would be possible to filter based on those two alternatives. Also adding a issue template with the master tag selected by default could be a good idea.

[Xyntexx]

Haven't tested this thoroughly but with a quick reading it should be possible.

[Xyntexx]

Also what about using the projects tab in github to plan out the roadmap to v7.0 etc?

[FantasyTeddy]

We tried using a project before, but it didn't add much value to the development process.

[FantasyTeddy]

I agree that adding an issue template would be good to get all the relevant information for reported bugs.

I'm not sure however, if labels (tags) are the right mechanism to specify in which version an issue should be solved.
Maybe we could use milestones for that?

[Xyntexx]

I meant that we could use labels to sort the issues found in released versions of AgOpenGPS and prioritize them over develop branch issues

[FantasyTeddy]

Yes, but I'm not sure labels are the correct way to do that.
I added a milestone Release 6.8 that can track all the issues that need to be solved in that release.

[Xyntexx]

I had AI generate some issue templates. You can test them out and leave a test issue at https://github.com/Xyntexx/AgOpenGPS/issues.
They are very excessive. What do we want to keep, and is there something missing? At least creating issues in the development branch should be way easier.

[Xyntexx]

I guess some templates for features etc too

[FantasyTeddy]

That's awesome.
Can you open a PR with those templates? Maybe as a "draft", so we can discuss anything that should be changed.