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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Maintenance mode should allow system admin to request process for internal test which stop usage for other users excpt admins
System: Product Urbancode Deploy v7112 Actor: System team admin needing maintenance mode feature not restrict testing for system team/admin users.
We commonly use the maintenance mode during any patching activity or critical issue faced during an outage.
Description: We recently upgraded to v7112 and extensively use maintenance mode during any admin activities, where during any upgrade/any critical activity if we face issues that has been reported critical , then we would need to stop users to further deploy & would need the system admins to test on the scenario further. Maintenance mode included from v7052 does not allow including the “System Team admin” to also trigger any deployments for internal testing done during outage/critical issue faced by users. As we(System team/admin) will have to test the scenarios internally but restricts to other users in production in such cases. This needs to be addressed as critical RFE as we are currently facing a scenario where self-approval is allowed even if the “no self- approval” restriction is enabled for the respective preprod & prod environment. We want to enable maintenance mode for just the other UCD users disabling permissions to not move any further with their deployment except the System Team admin users to further analyse the scenario in Production. So including this feature is very critical to any Urbancode Deploy users across the Globe. This scenario imposes a greater risk for production deployment to go through unless we restrict ourselves which stops us from further testing. There are many similar critical scenarios that stands with having this feature included in v7112.
System: Product Urbancode Deploy v7112
Actor: System Team admin user
Use cases for the system:
Maintenance mode enabled by System Team admin
Deployments not to be triggered by other UCD users
System Team to run test deployment for reproduce scenarios
Scenario: Enable maintenance mode restricts for other users but allows for System Team admins.
1. System Team enable maintenance mode in Settings page.
2. Maintenance mode takes effect & restricts other team users to further deploy.
3. System Team users should be able to work on the test/critical scenario faced/reported by users.
4. Test application to be able to be deployed with the scenario by the System Team users.
Do not place IBM confidential, company confidential, or personal information into any field.