Tuesday 31 March 2015

How to submit a Db2 feature/enhancement request/idea

- David Sciaraffa, IBM IM/DB2 Accelerated Value Leader (Premium Support Manager).

In the past, requests for functionality enhancements or new features for Db2 would have been facilitated through a Db2 sales professional, lab-advocate or AVP leader.

These requests can now be submitted directly by Db2 customers and users through the IBM Aha Ideas forum:   https://ibmanalytics.ideas.aha.io/


All requests are analyzed by DB2 offering and product development managers, and discussed with DB2 component architects for possible inclusion and prioritization in future releases.



Access the Aha Ideas forum here: 
https://ibm-data-and-ai.ideas.ibm.com/


Recent/Trending/Popular Ideas:

From the Header tab, you can view recent, trending, and popular ideas using the links shown:


Search for similar Ideas:

Before submitting a new feature/enhancement request idea, search for any existing similar ideas using the ‘Search’ box:




Any existing ideas that match your search criteria are displayed:

View an Existing Idea:

If your search results show an existing idea that is similar to the one you wish to submit, open the existing idea and click the vote icon to increase the vote count for this idea.  You can also add comments or details specific to your expectations using the 'Post a Comment' section at the bottom:

Submitting a New Idea:

If you do not find any existing ideas with your criteria, you can submit your own request using the ‘Add New Idea’ button

Within the new idea form:



Be sure to:
  • In the Choose a product for this idea box, choose 'Db2'.
  • Provide a clear and concise Idea Short Name (title).
  • Choose a Component which you think most closely relates to your idea. 
  • Provide a full and accurate description and use-case for your idea in the Details and How Should it Work text boxes. Use examples if possible.
  • Provide a realistic Priority value.  I would consider priorities as:
    Low = Nice to have. Lacking this feature has very little impact to the database solution.
    Medium = Lacking this feature has a small impact to the database solution, but can be worked-around in some (possibly inconvenient) way.
    High = Lacking this feature has identifiable impact to the database solution, causes highly visible grievances with the overall application solution.
    Urgent = Lacking this feature has direct impact to the viability of the database solution, and has immediate risk of breaking the overall application solution.
  • Provide an accurate Priority Justification. Consider describing how not having this feature will affect your business or Db2 as it’s strategic database solution. 
If you work closely with a DB2 sales representative, Lab Advocate, or Accelerated Value Program leader, please notify him or her when submitting a new idea.

View and Track Ideas:

When you are logged in, you can view your ideas, votes, and submissions using the ‘My Ideas’, 'My Votes', and 'My Submissions' links.







I hope this information is useful. If you have any thoughts or questions, feel free to submit a comment below. 

No comments:

Post a Comment

Translate