Open issues

Order by Priority
  1. Suggestion
    JIRAALIGN-7417Implement SSO in the public Ideation Portal
  2. Suggestion
    JIRAALIGN-4641Ability to Import Objectives
  3. Suggestion
    JIRAALIGN-8296Capability Planning View - Decrease Decimals on Member Weeks
  4. Suggestion
    JIRAALIGN-8103The "Why details" on the Jira is missing the Theme information. 
  5. Suggestion
    JIRAALIGN-6654The "Report Color" field has not been implemented consistently across all work items
  6. Suggestion
    JIRAALIGN-8085Enhance Jira Align connector log message - issue type is invalid
  7. Suggestion
    JIRAALIGN-8289Remove OKR Hub Toggle from Enterprise Level Navigation
  8. Suggestion
    JIRAALIGN-8293Prevent Closing Issues with Open Child Work Items in Jira Align
  9. Suggestion
    JIRAALIGN-8295Jira Connector - Improve Error Message When Custom Issue Type Entry Is Empty
  10. Suggestion
    JIRAALIGN-5691Expose Ideation Groups in API
  11. Suggestion
    JIRAALIGN-8184Able to import in bulk ideas via JA UI in the Ideation Portal
  12. Suggestion
    JIRAALIGN-8237Ability to add more options for Category in Ideation
  13. Suggestion
    JIRAALIGN-8236Manage Ideation Groups within the User Interface like Ideation Users
  14. Suggestion
    JIRAALIGN-4574REST API: Custom Field support for ideas
  15. Suggestion
    JIRAALIGN-6540Add the ability to delete an unused Jira connector from the JA UI
  16. Suggestion
    JIRAALIGN-7727Option to have a separate permission for 'Generate Team Sprints' button in PI slide-out Sync Sprints tab
  17. Suggestion
    JIRAALIGN-7824Enhancements to the Changes Log
  18. Suggestion
    JIRAALIGN-8288Add Portfolio Ask Date field in new Objective Experience
  19. Suggestion
    JIRAALIGN-5737Integrated Users Read Only the Portfolio Backlog
  20. Suggestion
    JIRAALIGN-5935Request to allow import of Risks and Dependencies via Excel
  21. Suggestion
    JIRAALIGN-6735Read-only view of Backlog
  22. Suggestion
    JIRAALIGN-6815Add Forecast Endpoints to API V2
  23. Suggestion
    JIRAALIGN-7953Add ability for changes in Jira to remove a Program Increment assigned to a story in Jira Align
  24. Suggestion
    JIRAALIGN-6601Ordering of options in dropdowns and custom dropdown fields
  25. Suggestion
    JIRAALIGN-6183Documentation Suggestion for the Epic Approval Functionality
  26. Suggestion
    JIRAALIGN-8284Add Column and Filter for parent to Prioritize (Estimate) back from Backlog in Jira Align
  27. Suggestion
    JIRAALIGN-8278Azure DevOps Connector - The connector should support ADO PI's iterations with the same date with different names
  28. Suggestion
    JIRAALIGN-6952Add calculated Forecasted, Estimated, and Accepted Spend data to Enterprise Insights
  29. Suggestion
    JIRAALIGN-7421Export more than 500 records
  30. Suggestion
    JIRAALIGN-8261As a Jira Align user I can create a work item specific checklist for capabilities so that I can ensure proper data hygiene in Capabilities
  31. Suggestion
    JIRAALIGN-7915Add Azure DevOps connector logs to Enterprise Insights
  32. Suggestion
    JIRAALIGN-5487Ability to link multiple Features to a single Dependency
  33. Suggestion
    JIRAALIGN-6883Parent Objective is not available during the creation using the old experience
  34. Suggestion
    JIRAALIGN-8279Change Budget field type on Epics to Long/BIGINT
  35. Suggestion
    JIRAALIGN-8007Add a Summary/Description field for Release Vehicles
  36. Suggestion
    JIRAALIGN-8281PATCH API request to cancel/delete a work items returns a success/204 when it should fail
  37. Suggestion
    JIRAALIGN-8280PATCH API request to send a work item to Recycle Bin fails
  38. Suggestion
    JIRAALIGN-6739Integrate Atlassian Intelligence with Jira Align
  39. Suggestion
    JIRAALIGN-7926Enable Feature split tracking and reporting between Jira Align and Jira
  40. Suggestion
    JIRAALIGN-8265New Roadmap: Roadmaps: Add objective type and category as a filter
  41. Suggestion
    JIRAALIGN-8274The initial sync between JA and Jira to create a weblink should respect the Connector sync direction settings.
  42. Suggestion
    JIRAALIGN-8276Feature Backlog - Kanban Column View - PI Load and Program Load should use consistent estimates
  43. Suggestion
    JIRAALIGN-7144Link Features (Jira Epics) and Dependencies for clearer dependency management
  44. Suggestion
    JIRAALIGN-5617Dependencies: enable ability to create a dependency between Epics, Features, Stories, etc.
  45. Suggestion
    JIRAALIGN-6082Request to add more granularity on the permission management for Dependency
  46. Suggestion
    JIRAALIGN-6093[Dependency] - Ability to add other work items when the Dependency is in progress
  47. Suggestion
    JIRAALIGN-6432Introduce "Add Feature" option to Program Dependency
  48. Suggestion
    JIRAALIGN-5831Deep linking on backlog list and kanban views
  49. Suggestion
    JIRAALIGN-8168ADO Connector - Support for Microsoft Entra OAuth
  50. Suggestion
    JIRAALIGN-8173REST API: Provide an Endpoint for ADO Connector Logs To Be Fetched
Refresh results
1 of 2714
Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-7417

Implement SSO in the public Ideation Portal

    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      It happens that Jira Align doesn't configure SSO for the public ideation portal.
      To log in to a public ideation portal, it use a simple email + password credential, which can affect security policy for some companies.

      Enhancement

      It would be important to have a feature in Jira Align to setup an SSO in the public ideation portal or use the SSO configured for Jira Align to access the public ideation portal.
      It would make the Jira Align safer.

            John Buchenberger added a comment - - edited

            Our ideation users generally are ...

            Dell team members with established authentication credentials coming from a field facing function (Support, Sales, Services) .  They are proxies to our customers.

            They typically would not already have a Jira Align license.  They are not developers or scaled agile leaders in the product organization.  

            We do not want to consume JA licensing for the purpose of idea submission.  

            We want the ideation users to be authenticated with corporate standard SSO as there may be sensitive information about customer and opportunity in the idea submission.  

            John Buchenberger added a comment - - edited Our ideation users generally are ... Dell team members with established authentication credentials coming from a field facing function (Support, Sales, Services) .  They are proxies to our customers. They typically would not already have a Jira Align license.  They are not developers or scaled agile leaders in the product organization.   We do not want to consume JA licensing for the purpose of idea submission.   We want the ideation users to be authenticated with corporate standard SSO as there may be sensitive information about customer and opportunity in the idea submission.  

              0aee7d7aac09 Juan Arias
              f9fc804f30c6 Luiz Felipe Arruda
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: