Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-10372

CreateIssueHandler: Add a group creation option to decide in which group the user will be automatically created

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      I want to manage incoming sale request from JIRA.
      Until now, ticket coming to the sale alias were created as "anonymous" user. The result is that I must answer with the email address included in the ticket and CC the sales alias to track the answer in Jira. If the customer answer to me only and do not CC the sales alias, his answer is not tracked.

      A solution to his problem is to automatically create its account. We can then answer / comment the ticket directly and the customer cannot reply to me directly and is forced to use Jira.
      It is not however possible to decide in which user group the user will be automatically created by the CreateIssueHandler. It is thus not possible to periodically look at this group to delete inappropriate users.

      I have played with the "Jira user" field in the global permission. However, as all user have to be in this group to be able to sign in, you cannot do a query to sort out the user that have automatically been created.

      This is a very important need and I feel the addition would be quite straightforward.

            [JRASERVER-10372] CreateIssueHandler: Add a group creation option to decide in which group the user will be automatically created

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3056117 ] New: JAC Suggestion Workflow 3 [ 3685234 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2608611 ] New: JAC Suggestion Workflow [ 3056117 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2561462 ] New: Confluence Workflow - Public Facing v4 [ 2608611 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2357629 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2561462 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2125003 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2357629 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2087427 ] New: JIRA Bug Workflow w Kanban v6 [ 2125003 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 883345 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2087427 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: pm200 New: affects-server pm200
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 709493 ] New: JIRA Bug Workflow w Kanban v6 [ 883345 ]
            Roy Krishna (Inactive) made changes -
            Backlog Order (Obsolete) Original: 11380000000
            Bugmaster Rank (Obsolete) Original: 12950000000
            JIRA Support Rank (Obsolete) Original: 87680000000
            Studio Rank (Obsolete) Original: 14030000000
            Support Rank (Obsolete) Original: 14030000000
            Workflow Original: PM Feature Request Workflow [ 223675 ] New: JIRA PM Feature Request Workflow v2 [ 709493 ]
            Issue Type Original: New Feature [ 2 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

              Unassigned Unassigned
              faa7ecd34d17 Mickaël Rémond
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: