Migrating from the legacy Ideas application to Idea Portal
Summarize
Summary of Migrating from the legacy Ideas application to Idea Portal
When upgrading to the Yokohama release, you must complete specific migration tasks to start using the new Idea Portal. This involves updating configurations related to idea states, categories, conversion options, business rules, and navigation to ensure a smooth transition from the legacy Ideas application.
Show less
Idea States
The new Idea Portal introduces updated idea states such as Completed, Under Review, and In Backlog, which map to your existing legacy idea states. Starting with Yokohama, idea states are stored and retrieved from the Idea [imideacore] table. You can continue using legacy states alongside new ones, or choose to delete old states via the Choice [syschoice] table to exclusively use new states for idea management.
Idea Categories
Ideas should be organized into categories to group them by product, department, or business unit. If your existing ideas lack categories, you can create new ones or use default categories installed with the Ideas application. For ideas already categorized, you can map existing categories to the new default categories and use scripts to establish many-to-many relationships between ideas and categories. Proper category mapping is essential for ideas to appear in the new Idea Portal.
Converting Ideas to Work Items
The new Idea Portal allows conversion of ideas into various work entities beyond demands, including projects, epics, and stories. This functionality is accessed via the Create Task button on the Idea form and requires Agile Development 2.0, Scaled Agile Framework (SAFe), and Continual Improvement Management plugins. If you prefer limiting conversions only to demands, you can disable the Create Task button and control workflow with Accept or Defer buttons.
Business Rules
Review existing business rules on the idea table after migration. Disable any business rules that should no longer apply by setting them to False to avoid conflicts with the new portal operations.
Navigation for Legacy Ideas Application
To promote usage of the new Idea Portal, remove navigation links to the legacy Ideas application from the application menu and deactivate the Submit an Idea option in the Service Catalog. This encourages users to submit ideas using the updated portal interface only.
If you are upgrading to the Yokohama release, complete the migration tasks after the upgrade to start using the new Idea Portal.
Review the following information and make any necessary changes to your configuration:
Idea States
| Idea State | Value |
|---|---|
| Draft | -5 |
| Submitted | 1 |
| NA | NA |
| NA | NA |
| Accepted | 2 |
| NA | NA |
| NA | NA |
| Closed complete | 3 |
| Closed skipped | 7 |
| NA | NA |
| NA | NA |
| Idea State | Value |
|---|---|
| Draft | -5 |
| Submitted | 1 |
| Under Review | -1 |
| Need more information | -2 |
| In Backlog | 2 |
| Planned | 4 |
| In Development | 5 |
| Completed | 3 |
| Unlikely to Implement | 7 |
| Duplicate | 8 |
| Already Exists | 9 |
Starting with the Yokohama release, idea states are stored in and retrieved from the Idea [im_idea_core] table. You can continue to use your existing idea states along with the new idea states. However, if you want to use only these new states for managing your ideas, navigate to the Choice [sys_choice] table and delete the old idea states.
Idea categories
Organize your ideas using categories, for example, to group ideas that are relevant to a particular product, department, or business unit. If your existing ideas are not associated with any category, create new categories or select an existing table to define categories to which you can map your ideas. The Ideas application also installs a set of default new categories to which you can associate your existing ideas.
Converting ideas to demands or project, stories, initiatives, and epics
You can convert an idea into work entities other than demands. The Create Task button enables you to convert an idea into a project, epic, or story as well as a demand becomes available in the Idea form.
You must have the required Agile plugins Agile Development 2.0 and Scaled Agile Framework (SAFe) and Continual Improvement Management installed to view these options.
If you want to allow conversion of ideas only to a demand, disable the Create Task button and continue using the Accept button or disable the Accept and Defer buttons to use other options. For more information see, Using the form designer.
Business rules
Review the existing business rules in the idea table. Set the business rules that you don't want to apply as False.
Navigation for legacy Idea application
To encourage your users to submit ideas through the new Idea Portal, remove navigation for old Idea application from the application menu and deactivate the Submit an Idea option from the Service Catalog. For more information see, Enable or disable an application menu or module.