Issue Details (XML | Word | Printable)

Key: JRA-14259
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: tim feeley
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

More customizable UI: Screens and "Core" Pages

Created: 10/Jan/08 10:26 AM   Updated: 10/Jan/08 10:57 PM
Component/s: Plugins - Issue Views, Portlets, Renderers, UI / Usability
Affects Version/s: 3.12.1
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. screenshot-1.jpg
(101 kB)
Issue Links:
Reference
 

Participants: Anton Mazkovoi [Atlassian] and tim feeley
Since last comment: 38 weeks, 5 days ago
Labels: ui screens upgrade customize


 Description  « Hide
To allow more system-managed customization of JIRA's interface, consider providing a more "robust" editor to customize elements of transition screens as well as issue view screens.

I know there's some plugins that allow for Velocity processed messages, but if we had the ability to control areas of the screen (conditionally, perhaps), I know it would reduce the number of modifications needed to the main JSP pages.

(This is just part of my series of suggestions for making upgrading easier for those of us with customized configurations - sorry for the several linked tickets!)



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
tim feeley added a comment - 10/Jan/08 10:27 AM
Sample SharePoint-esque way of allowing reorganization of a view/screen. Ideally, each "component" would have properties (such as Display To: user group/roles, Editable By: user group/roles).

I know a lot of these tickets have been requested as one-offs, but this is just attempting to capture several requests and link it to a larger issue at hand.

Thanks


tim feeley added a comment - 10/Jan/08 10:30 AM
Part of the bigger picture (JRA-14240) - this would just be a component of "easier JIRA-tracked customizability that would be retained during upgrades."

Anton Mazkovoi [Atlassian] added a comment - 10/Jan/08 10:57 PM
Tim,

Would most of this ticket be covered by JRA-4913?

We appreciate your feedback. Please note however, that we have thousands of improvement and new feature requests. While we would like to do most of them, we, unfortunately, will never get the required resources to do so. Aggregating information helps us to better schedule issues that fit with the direction of the product and bring the most benefit to our users as described here:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

Therefore, if JRA-4913 does cover what this tickets discusses, could we close this as a duplicate?

Please note that providing security over each issue field is covered by JRA-1330, which we are not planning to implement. Please see JRA-1330 fore more details on this decision.

Also, please note, our aim for JIRA is to ensure that it works out of the box. It is very difficult to make everything conditional and configurable and still enforce consistency and data intergrity. JIRA is not mean to be a toolkit where one needs to invest 100s of hours of development work to get things just to run.

Due to this, some things are not possible to get to work exactly how you need them oy of the box. Often, it is possible, and worthwhile to customise JIRA to do them. However, customisation will incur addition cost when upgrading. Whether this is worth it, depends on how important the requitement is.

Please let us know if JRA-4913 or JRA-9802 address this request.

Cheers,
Anton