Please indicate in the main issue page that files may be uploaded in the next page.

we actually do indicate how to upload a file on the bugs and issues page, <http://qa.openoffice.org/
issue_handling/project_issues.html> and cannot change the particular page you refer to.  closing with 
wontfix. This menas that I can't do anything about it.
Louis

Right, with the current possibilities for customization we are not able to add
such a hint.
So we are asking for a way to add (HTML-) text at the top and/or bottom of
IssueTracker (or successor) forms.
There should be a way to add text to a specific form (enter, query, show, ...)
or to all.
Changed summary accordingly.

reassign to support

We would have to consider this for the Project Tracker product as IZ is not
being enhanced going forward.

Would this request to add help text to issue tracker be particular for each type
of issue?  Within each project?  Just for the system as a whole?  Would it be
just text?  Would particular fonts/styles need to be supported?  Would it extend
into the administrative forms of the issue tracker?  Would the added text be
seen by everybody or only people with certain permissions?  Who should be
allowed or disallowed to add the text?

We need more descriptive information about how to define this request.

I think a mechanism like the remote branding capabilities would be appropriate
to fulfill our requirement. It should allow the addition of HTML text at the top
and/or bottom of each form (new, edit, query, view, report, ...).

But let me try to answer your questions...

> Would this request to add help text to issue tracker
> be particular for each type of issue?
That depends on the structure of the tracking system. IZ/IT has forms for
different actions and uses them for all types.
If PT has different forms for different issue types it might make sense to add
text per issue type and not per action.
But we should keep the number of places for text additions manageable.

> Within each project?
> Just for the system as a whole?
For the system as a whole would be a good start.
In general I like the approach to provide system defaults and allow a project to
override those.

> Would it be just text? Would particular fonts/styles need
> to be supported?
Usage of HTML would be helpful.

> Would it extend into the administrative forms of the issue tracker?
No, I don't think that's needed.

> Would the added text be seen by everybody or only people with
> certain permissions?
By everybody with permission to see the page/form in question.

> Who should be allowed or disallowed to add the text?
IZ Administrators and/or the users allowed to work on remote branding.

The business impact is that we could save much work we currently have to spend
on incomplete, incorrectly handled issues by providing site specific at this
prominent place.

I have submitted an internal issue to get this reviewed with the detail we have
so far.  I will update as other details are questioned or need clarification.

Hi,

Anything that is created will be under the control of permissions/actions that 
OO will be open to assign to roles as you desire. 

Given the way that artifact types are managed today there will be "global" 
administrators who set up the text for the artifact type "templates" and then 
project level administrators would then be able to make project 
modifications.  If this is not the model envisioned then we would like to know
the   model you are looking at.

Regards,
Ramya
Support Operations

The model as such sounds good, but it's not applicable to IZ.
I assume you are refering to Project Tracker. Could you elaborate which
branding/customization options for artifact templates PT offers?

Yes, I was referring to the Project Tracker.In Project tracker, the Domain admin
will be able to create an artifact type(ie. a template),which can be used by any
the Project Administrator on his project, by customizing the template( ie.
modifying the field names provided in the template).Please feel free to get back
to us for further clarifications.

Regards,
Ramya
Support Operations.

So you might want to mark the issue with a target milestone that reflects the
release containing a PT version suitable for OOo.

To CRM

>>>So you might want to mark the issue with a target milestone that reflects the
release containing a PT version suitable for OOo.

Absolutely.

Regards,
Ramya
Support Operations

This particular feature is already available in Project Tracker via the
show/hide button for artifact entry pages.

Hence moving this issue to the resolved later queue

CollabNet Support is currently reviewing the issues under Resolved-Later. If the
issues are fixed currently in any of the present CEE releases, then it will be
marked as Resolved-Fixed.

There might be a few issues which might not be in our future roadmaps which
might be closed as Wontfix unless it does not lie under any custom request.

This feature is available in PT. Though PT is not enabled on OOo, Collabnet has
fixed this in PT which was developed with IZ as a base