Launchpad itself

Bug to project identification is very poor

Asked by Flynt

Recently some Infrae projects switched from Roundup as Issue-Tracker to Launchpad. In contrary to other bug-trackers an identification in the email messages of a certain bug with a certain project is poor or not given at all. This means we have to track the relevant bugs again for ourself.
If Launchpad wants to be used for different projects, it would be the least to care for a clear naming convention to make a difference between bugs of different projects.
As it is dealt with right now the mechanism is insufficient and I consider this a major drawback of Launchpad in regard to day-to-day work as a project manager. It practically forces me to operate a second tracker or at least a list of "my projects" bugs.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Christian Reis
Solved:
Last query:
Last reply:
Revision history for this message
Christian Reis (kiko) said : 		#1

Thanks for the feedback. I think I need to understand your problem better. Right now, we offer two headers which allow you to do discrete identification (and filtering) of your bugmail. They are X-Launchpad-Bug and X-Launchpad-Message-Rationale. Let me show you some documentation... here: https://help.launchpad.net/UsingMaloneEmail#head-9313c7b25665327a080cb976ca05bfca8aaad30a

How can we improve this further for you?

Revision history for this message
Flynt (flyntle) said : 		#2

My fault, sorry! I forgot an imortant detail:
I am talking about an identification in the

- subject field

of the message. So I am talking about a simple visual help for connecting a certain message with a certain project.
Is there a possibility of getting something there?
Or do you think that the subject field's content would get too long?

Revision history for this message
Best Christian Reis (kiko) said : 		#3

One problem with putting the package or project name in the bug summary is that for bugs that are open on multiple contexts (for instance, a bug filed against Ubuntu and Silva), we would have to string them along in an awkward manner.

I feel that putting the project name on the subject line also makes it a lot less scannable, because you get the same text there repeated when looking at a set of bugs in the project. I deal with a great many bugs filed against the same project, so filtering using the header is the best solution for me. I'm not sure that matches your use case, though.

If you have opinions or suggestions to share the right way to move forward is to comment on the bug that Matsubara linked here: https://bugs.launchpad.net/bugs/36586

I hope using the header is a valid workaround for your immediate problem. Thanks for the feedback.!

Revision history for this message
Flynt (flyntle) said : 		#4

Thanks Christian Reis, that solved my question.

Revision history for this message
Flynt (flyntle) said : 		#5

I would like to add, that I am impressed by the speed of reaction, the effort and the quality of the answer.
Many large companies would not be able to compete with this quality of service.
Congratulations!