IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM Engineering - Workflow Management
Categories Work Items
Created by Guest
Created on Feb 19, 2019

RELATED IDEAS

Want a field in the work item that displays the date when the work item moves to in progress

We have programs where work items sit in the new state for long periods of time. We want to easily view on the work item when the item actually moved to the in-progress state. The need for this is for some programs to do an export of work items and create a metric. But for other programs they want to view it in order to push for progress. This shows in the history which is not readily accessible. It also shows in JRS but this is not something that can be seen in the work item and also has a delay because of the warehouse. Originally submitted under TS001805491.

Idea priority Medium
  • Post comment
  • Guest
    Reply
    |     Oct 7, 2022
    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The IBM Engineering team has carefully reviewed this idea, and based on our understanding, even though the request aligns with our modernization vision but is unlikely to be addressed in the near-term due to other higher priority items on the Backlog. Although we are closing this request, it will be kept in IBM's ideas repository. We value your feedback and thank you for allowing us to partner with you in developing our products.
  • Guest
    Reply
    |     Mar 4, 2019

    RFE Review board looked at this and decided to leave it in the product backlog. It has been linked to a feature work item in our product backlog.

  • Guest
    Reply
    |     Feb 24, 2019

    As I have been working this issue for several programs another issue has cropped up. As I said earlier I am able to get the date though a JRS query, which is not intuitive but can be done. What the ultimate goal (for some programs, not all) is they want to know how many days each completed work item was "in progress". In JRS Data Warehouse this is easy to do in the advanced query section. However in LQE (which I am told is where all the data is going in the future) there is no way to get an exact answer of the number of days between 2 dates that I can figure out. If there is it will be complicated, I know that. The report can be exported to Excel and calculated there but this is a two step process and is annoying to my users. In trying to figure out an algorithm to implement in SPARQL none gives a reliable day difference. They all are +-2 to 3 days. One algorithm where the dates are converted to Julian days and the two Julian days are subtracted (which is supposed to be the most accurate but yields no better results) However, the algorithm is 675 characters long! Now while I know very little about SPARQL, I think that is the case of most users. SPARQL is not trivial to learn especially when your main goal is to work your project and manage your team. If we have a start date in the work item we can very easily write a calculation java script that will give an accurate answer.

  • Guest
    Reply
    |     Feb 20, 2019

    Actually, I think it would be more useful, instead of making 1 status change have a query-able date, make the history query-able. That way you could search for the date and time of any status change.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.