Use simple yet unique titles: you want the title to be simple and easy to grasp, and you don't want two bugs to have the same title.
However, a bug summary should be synthetic. No need to specify the path or part of the description in it.
Although you need to be concise, you should include some key words or info (string IDs) in your summaries.
On the other hand, for No duplicates (also known as "dupes"), you don't want to create an entry for an issue that is already covered.
Hey Jon,
Hope you’re doing awesome!
We need to team up with the Dev squad to get our CGG features rolling. Here’s what I would consider to make it happen:
1. Let’s set up a chill meeting with Dev to share our goals and see what’s up on their end.
2. We should whip up some clear docs with all our needs and specs to keep everyone on the same page, although it might be challenging.
3. Even though we are super busy at the moment, Let’s do regular updates to keep things on track and tackle any blockers fast.
4. Keep the convo going and get their feedback. Despite of the fact that it will take some time, It’ll help us tweak things and make the process smooth.
5. Chat early about what we need from both sides so no one’s overloaded.
LMK what you think or if there’s anything else we should throw in.
Catch you later,
