Issue Details (XML | Word | Printable)

Key: JRA-9417
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Benjamin Naftzger [Atlassian]
Votes: 4
Watchers: 3
Operations

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

JIRA portlets should be JSR-168 compliant

Created: 21/Feb/06 10:52 PM   Updated: 07/Nov/06 05:13 PM
Component/s: Portlets
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Benjamin Naftzger [Atlassian], Nick Menere [Atlassian], Noam Field and Thiago Rossato
Since last comment: 1 year, 48 weeks, 4 days ago
Labels:


 Description  « Hide
As many portel products use the JSR-168 standard for portlets, it would be very beneficial (from an interopability point of view) to ensure that all JIRA porlets were JSR-168 compliant. Customers could then easily add JIRA portlets to their portals.

http://developers.sun.com/prodtech/portalserver/reference/techart/jsr168/



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Benjamin Naftzger [Atlassian] added a comment - 21/Feb/06 10:54 PM
The customer highlighted the 'issues assigned to them', 'project statistics', 'watched issues' porlets as priority.

Thiago Rossato added a comment - 25/Aug/06 03:44 PM
I think that the "Show Saved Filter" portlet is important too.

Do you have any plan to support JSR-168? When?

Thanks,
Thiago Rossato


Nick Menere [Atlassian] added a comment - 27/Aug/06 08:14 PM
We are looking at improving the dashboard and general portlet functionality, though I am not sure that this will be included. I will have to check.

Noam Field added a comment - 07/Nov/06 05:13 PM
The following plugin mentions that it is a JSR-168 compliant portlet for JIRA:

http://confluence.atlassian.com/display/JIRAEXT/Kosmos