Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 252505

Summary: custom text field not shown in task editor when field does not have a value
Product: z_Archived Reporter: Tom Jordan <tdjordan>
Component: MylynAssignee: Mylyn Inbox <mylyn-inbox>
Status: RESOLVED NOT_ECLIPSE QA Contact:
Severity: normal    
Priority: P3 CC: robert.elves, steffen.pingel, wseliga
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
URL: https://studio.atlassian.com/browse/PLE-909
Whiteboard:
Bug Depends on:    
Bug Blocks: 249057    
Attachments:
Description Flags
Snap of JIRA's web editor showing the field as requred
none
with existing data in field
none
without prexisting data none

Description Tom Jordan CLA 2008-10-28 17:47:04 EDT 
A blank "Affected Feature" which is a required field is not showing up in the Attributes pane of the task editor.

JIRA server version: 3.12.1 - #299
Eclipse version: 3.4
JIRA connector version: 3.0.3.v20081015-1500-e3x
Comment 1 Tom Jordan CLA 2008-10-28 17:49:06 EDT 
Created attachment 116362 [details]
Snap of JIRA's web editor showing the field as requred

Snap of JIRA's web editor showing the field as requred
Comment 2 Tom Jordan CLA 2008-10-28 17:52:18 EDT 
Created attachment 116363 [details]
with existing data in field

This shows an issue that already had something in the required field.

The editor shows the filed as editable
Comment 3 Tom Jordan CLA 2008-10-28 17:54:12 EDT 
Created attachment 116364 [details]
without prexisting data

without prexisting data, the required field doesn't show up to put something in it.
Comment 4 Steffen Pingel CLA 2008-10-28 17:55:35 EDT 
What kind of field is Affected Feature?
Comment 5 Tom Jordan CLA 2008-10-28 18:02:50 EDT 
(In reply to comment #4)
> What kind of field is Affected Feature?
It is a custom string field
Comment 6 Steffen Pingel CLA 2008-10-28 18:26:49 EDT 
The problem is that information about custom fields that do not have values set is currently not returned by the repository (see also bug 203555).
Comment 7 Steffen Pingel CLA 2009-06-20 16:32:05 EDT 
Wojtek, you mentioned that you had some ideas to make improvements here?
Comment 8 Wojciech Seliga CLA 2009-09-14 14:49:08 EDT 
Finally we had time to take a closer look of what we can get with current (JIRA 3.13.x) remote API.

Jacek put his findings at https://studio.atlassian.com/browse/PLE-663

I have to agree that API sucks here as it either does not return field type or does not return field info when it's left blank.

Hoping for really incoming new REST API, we should rather refrain from using various hacks (like screen scraping edit issue screen) and implement it properly when missing server functionality is in place.
Comment 9 Steffen Pingel CLA 2010-02-27 20:17:48 EST 
The Mylyn JIRA Connector has moved to Atlassian. All unresolved Mylyn bugs assigned to the JIRA component, which includes this bug, have been copied to https://studio.atlassian.com/browse/PLE and marked as resolved on bugs.eclipse.org. The new location of this bug report can be found in the URL field. 

Please see this FAQ entry for further details: http://wiki.eclipse.org/Mylyn/FAQ#What_happened_to_the_Mylyn_JIRA_Connector.3F .