Jack Brickey Expert

Without understanding the solution for the incoming email address it’s hard for me to come up with a automation solution. However I can say that if you can access the email through some custom field or otherwise then you can certainly use the JQL query condition Automation to allow you to sign the issue to the proper person

Generally speaking I would not create duplicate fields. I think changing the request type is fine. the priority is a bit more sensitive but if you have a clear policy on priorities then I think it’s fine to change the priority as well. However if you feel that sends the wrong customer message then consider creating a new…

I have never seen that be successful. Please share where you read about this being successful. Success of that aside, for automation to work you’re gonna need to be able to access the email address. So you gonna need to figure out where that address can be found. When you’re working with the single email address that Jira…

Can you share your boards filter here? You will find it under board settings general. Also it would be interesting if you use that filter and just do a JQL advanced search do the two issues show in the results?

Hi Avi, Jira service management works with a single email channel. So I’m unsure how you have or plan to achieve allowing it to function with two separate email channels. Can you explain this a bit to me. 

Do you want to use a custom field for that.

you need to go into the workflow and add your status there. Then go into the column section under board settings and map the status to a new column. 

Yep. Just create a new scrum board that is based on the same Kanban filter and you are good to go. You can delete the Kanban board when you are happy wit the Scrum board. 

What is exactly does scrumban mean to you? You likely can achieve this is simply using the scrum board. 

Oh I see those are just comments. The field is a system field called comments. You can’t add comments column however you can export the report and include them. 

Someone has incorrectly set the resolution field as required in the field configuration. This is bad practice as you clearly do not want to set the resolution at the time you create an issue. Go to the field configuration for the project find the field and change it from being required. 

You can add a validator to the workflow transition. So if you want someone to fill in the field whenever an issue is moved to done you would add a validator to any transition into the done status. Pick the field that you want the validator to require and add an error message if you choose as well. Note that this is…

And note that you are limited to three fields that can be added to a card. 

You would need to export data from mingle into a CSV file that could then be massaged and used to import into Jira. 

I’m not familiar with internal notes. Maybe this is a custom field that you have defined? If so, you should be able to extract that information with JQL filter results. 

Unfortunately not. You may want to watch and vote for this issue JRACLOUD-72263 

It may be that the issue was deleted. Are you able to see other issues for the same project?

You should consider using automation for this. In fact if memory serves there may be one in the library already for it that you can use as a starting point. Basically you want to have an SLA set up for non-responsive customers. And when that SLA breaches then you can trigger an automation to remind them

You can’t disable it like he used to be able to. There is a setting under your avatar called personal settings and in there you’ll see your labs but it will give you a message telling you about the transition to the new Issue view. 

Regrettably no there is not. At least not that I have found. 

If the replies or done to the original email that creates a ticket and not to the response back from Jira about the creation of the ticket then a new ticket will be created. The key to this is the issue key for the issue created must be in the subject for it to equate to a comment. 

Unfortunately that option does not exist without an addon. 

Your proposed approach is , IMO, the correct approach. 

For me and my team planning is done in Backlog. Planning equates to defining what the team commits to achieve in a sprint. Starting a sprint signifies the end of planning. When the sprint starts the team will begin working on issues in the to do status moving them to in progress and eventually done and pull the next to do…

You can use request-channel-type on JQL for this. You cannot add values to this field. 

I think you’re losing me here. In any of my active sprints I will only see the issues that I have moved into the sprint. I never see any true backlog issues in my active sprint. What I will see in the backlog page in the top section are any issues that are still in progress in active sprint. Please note I only use classic…

For scrum boards any backlog items will not display on the active sprint board until they’re actually moved into the sprint and sprint started. Are you seeing something different?

In your screenshot on the left-hand side you see the ONB Dash number. And there’s an icon just to the left of that can you click on that icon? example of what I see. I am Mobile and on my phone which makes it difficult for me to assist had a desktop client level

You will see it in the detailed issue of you not in the queue view. It should be in the breadcrumbs at the very top

I would suggest using automation to achieve this. I would trigger on the transition And assign based on your conditions