Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319533 - Piggy-backing does not always fill in summary and version correctly
Summary: Piggy-backing does not always fill in summary and version correctly
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: IPZilla (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Foundation IPZilla inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-12 07:01 EDT by Glyn Normington CLA
Modified: 2017-03-27 12:43 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 2010-07-12 07:01:23 EDT 
See for example CQs 4321 and 4324.

I entered these by searching for the CQs on which I wanted to piggy-back from the portal and then selecting the CQ to piggy-back on, entering some text, and answering the source/binary and modification questions. Usually this populates the summary and version of the new CQ correctly, but this failed in the cases above.
Comment 1 Eclipse Genie CLA 2014-11-30 16:23:02 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2016-11-20 15:56:53 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Wayne Beaton CLA 2017-03-27 12:43:48 EDT 
I believe that this has been addressed by the PMI-based implementation.