Requesting a New Feature or Feature Improvement

This article documents how to fill out and manage a feature request LPS ticket in JIRA (the Liferay Issue Tracking System).

In case you have an idea for a new feature that is not yet implemented in the Liferay platform, or you would like to improve one of the already existing features, it is a good idea to create a feature request LPS ticket. 

Resolution

First of all, you will need an account in JIRA. If you do not already have an account, feel free to register yourself. After this, take a moment to search through existing tickets to see if any other users may have requested the same feature already.

Searching for Existing Feature Requests

The best way to perform this search is to use the Feature Request Dashboard. Here you can use the search field, and several feature requests are listed already by various aspects: latest ideas, most popular ideas, features that are currently under development, requests that have been resolved recently. On the right side of the dashboard there is a list with all of the Feature Areas / Technical Components in Liferay (for example: Web Content Management, Collaboration, Security, and many more), along with the number of feature requests created in that area. Clicking on the name of a component will reveal a list of feature requests in that area. 

It is also possible to search directly on JIRA. Look for LPS tickets with Issue Type Feature Request. If you are not familiar with the search feature in JIRA, please check this Knowledge Base Article for instructions:  How to Search for Known Issues for Liferay Portal

If you did not find an already existing request for the same feature, there are two separate ways to create a feature request LPS yourself. You can either use the Feature Request Dashboard or JIRA itself. 

Creating a Feature Request Using the Feature Request Dashboard

On the dashboard's right side there is a list with all of the Feature Areas in Liferay. Clicking on the "+" icon next to the Feature Area will allow you to enter a new Feature Request. You can also click on the Submit Feature Request button on the far right side if you prefer to select the technical component later. After this is done, please fill out the form:

  • Summary: This will be the title of the ticket. Please try to summarize the goal of your request in one short sentence.
  • Component/s: Please select one or more component for the ticket based on the technical area where the feature that you request belong. (This is filled out by default if you selected a Feature Area beforehand.)
  • Description: In this field please explain why this feature would be beneficial in the core Liferay Platform or as a Marketplace Application. A good description should include relevant information such as background information, the need for such a feature, pertinent use cases, expected outcomes, and any other information that is useful to one who is considering the request.

Creating a Feature Request Using JIRA

  1. Navigate to http://issues.liferay.com.
  2. Sign in with your account.
  3. Click on the Create button in the dockbar at the top, and select the following options:
    • ProjectPUBLIC - Liferay Portal Community Edition
    • Issue TypeFeature Request
  4. Fill out the form:
    • Summary: This will be the title of the ticket. Please try to summarize the goal of your request in one short sentence.
    • Component/s: Please select one or more component for the ticket based on the technical area where the feature that you request belong.
    • Description: In this field please explain why this feature would be beneficial in the core Liferay Platform or as a Marketplace Application. A good description should include relevant information such as background information, the need for such a feature, pertinent use cases, expected outcomes, and any other information that is useful to one who is considering the request.

Promoting a Feature Request Ticket

If you found an already existing ticket for the same feature request, in the right side you can click on Vote for this issue button to indicate that you are also interested in that feature, and you can also click on Start watching this issue button to get a notification about the progress on the ticket. It is also a good idea to leave a comment there to emphasize your requirement (this way participants and watchers will get a notification). In case you are the reporter of the ticket, this is not necessary.

After you are done with the ticket itself, let the community know about this request. The more people learn about your proposal the more feedback you will get and the more people will comment and vote for your feature. Feature Requests with more votes and activity will always have a better chance of being implemented sooner. Here are some ways in which you can promote these feature requests:

  • Tweet it
  • Like it on Facebook
  • +1 it on Google+
  • Mention it on the Liferay Forums
  • Talk about it in any event or conversation with people interested in Liferay

The Feature Request Dashboard includes convenient links for posting of yours and others' ideas to your favorite social media networks.

Liferay Inc. will periodically review a subset of the submitted feature requests (based on criteria such as number of votes), and determine whether or not to implement the feature itself. If Liferay Inc. decides to implement the feature request (either in the core platform or as a Marketplace App), the status of the feature request will change to Selected for Development, and a separate workflow (beginning with the creation of one or more linked Story tickets) will be filed. After this, the normal Liferay software development process will see it through to the next major Liferay release. However, if Liferay Inc. does not desire to implement the request itself in the next major Liferay release, the Feature Request will remain Open. 

Liferay Inc. does not reserve the exclusive right to ideas that it decides to implement itself. If you wish to implement an idea that Liferay Inc. has also decided to implement, go for it! All ideas, whether or not implemented by Liferay Inc., must pass through the same quality and relevance filters that any software feature must go through, before being included. Liferay Inc. will not implement every feature request - through this open process, the community can see exactly what people are looking for, and can evaluate the suitability of the feature for themselves, and promote it, or take the extra step of implementing it as a core contribution or a Liferay Marketplace App.

Additional Information

Was this article helpful?
1 out of 2 found this helpful