Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Hi I'm Dan Bogowitz

I'm in the QA Manual Class.

 

6 comments

Brant Schroeder Community Leader Mar 29, 2021

@Dan Bogowitz Welcome to the community.  

Dan,

I have a need for this question below and please response back with instruction how to go about it.

 

  1. We asked Atlassian, “Does their next higher version of Jira SM provide for more email integration functionality?
    1. Atlassian said, “This is already exists. See the "Receiving requests by email" in this Link 
    2. We Go to that link. It says, “Set up a suitable request type with Summary and Description as required, visible fields. Any other fields must be optional.” 
    3. What does “any other fields must be optional” mean? It seems to imply that they can pick up other information from the email. This is important to investigate.
  1. Can we rename the Priority field to Severity?
  2. Need to find out if there are separate fields for saving name, email and number; it’s terrible to have to put all of this in a free form field
  3. We need to know everything about their email integration
  4. Does their next higher version of Jira SM provide for more email integration functionality?
  5. Can we assign a ticket to a group called Level 2, and in Jira the Level 2 personnel would be able to see the tickets assigned to that group, and they would “pull” the ticket from the group…..and basically assign it to themselves?

Well her is my Manager's respond to the answers you guy had provide to us yesterday.

  1. Can we rename the Priority field to Severity?
    • No, it's not possible. You can create a custom field and Rename to Severity, and using Jira Automation copy the values.
    • Tommy: Use the Priority field but the only available values for this field should be 1, 2, 3, or 4.
  2. Need to find out if there are separate fields for saving name, email and number; it’s terrible to have to put all of this in a free form field
    • Use custom fields with single text line (255 characters) to generate this need of business/report
    • Tommy: Need to do this. The Reporter field is not long enough to support name, phone, and email address.
  3. We need to know everything about their email integration
    • You can use advanced search in Jira (JQL) to find emails and/or you can look on the customers of JSM to see the tickets opened by that email
    • Tommy: By “email integration” I meant that we needed to know the full capabilities of opening a ticket from an email. Do they have a template we can use that they then pull the data from? Other than the fields that we know they pull from the email and into the ticket, are there any other fields that they can pull from?
  4. Does their next higher version of Jira SM provide for more email integration functionality?
    • This is already exists. See the "Receiving requests by email" in this Link 
    • Tommy: Go to this link. It says, “Set up a suitable request type with Summary and Description as required, visible fields. Any other fields must be optional.” What does “any other fields must be optional” mean? It seems to imply that they can pick up other information from the email. This is important to investigate.
  5. Can we assign a ticket to a group called Level 2, and in Jira the Level 2 personnel would be able to see the tickets assigned to that group, and they would “pull” the ticket from the group…..and basically assign it to themselves?
    • No, a issue can have only ONE assignee. but  you can assignee the issue using to one group of users using the automation, below, I send the 3 types of configuration that automation supports has for this configuration (Link )
    • Tommy: Investigate this and see how it needs to be set up. For now I would use Balanced Workload. But we need to know how the Level 2 person pulls themselves out of the group of users if they are going to be out of the office…can’t assign a ticket to someone that’s not working that day.
      • Balanced Workload: Ensures that each user in the list has the same number of issues assigned.
      • Random: Assigns randomly from the list of users.
      • Round-Robin: Assigns issues based on the sequence in the list of specified users.

Hi @Dan Bogowitz 

Welcome to the Atlassian Community!

Erica Moss Community Manager Mar 30, 2021

@Dan Bogowitz Welcome to the Atlassian Community! Be sure to check out the product collections that interest you, as well as our member journey and Friday Fun. 😄

Like Fadoua likes this
Fadoua Community Leader Mar 30, 2021

Welcome @Dan Bogowitz ! We will all be happy to assist in anyway we can.

Taranjeet Singh Community Leader Mar 30, 2021

Welcome to the Atlassian Community, @Dan Bogowitz ! Hope you have a great learning experience here!

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you