Jack Brickey Expert

Thanks @Viktoriya Borisova , it has been a fun filled events November. My latest attendance was Sam's demoing CMP vs. TMP. He did a great job of illustrating the pros and cons of the two solutions. He presented from Lansing Michigan and I participated from Sanford NC.

Wendy, have a look at this video demo - https://youtu.be/gyHCj84_ZwQ 

if you are asking if you could have dynamic conditional form fields, the answer is Yes you can. When you create the form, you can add a new section in that section can be dynamic and conditional upon a given field and what is selected in that field. It's pretty straightforward to set up. what-are-forms 

Hi @Rafael Brasil , the Automation audit log shows removed rules as Config change.

Hi @Callum Breen Begadon , you will need to reach out to Atlassian support to see if they can assist here.

Please verify that the "request type" is set.

@Benjamin Lellouche , so I misunderstood your goal based upon the initial post. In your last reply, it seems that you wish to close the epic once all stories are closed under that epic there is actually a rule in the library that is very close to what you need. It looks like below. You will need to add in your unique…

Ok should be pretty straight forward I think. Can you give the rule a try based upon my previous guidance?

My given name is Jonathan. Meanings include: Gift from God, God's given, or a handful of other variations. I'll take it! 😉

Hi @Kevin Ostheimer , with JQL you can't have any query functions after the Order by. So try this... project = myproject AND reporter = currentUser() and type = epic ORDER BY created DESC

Hi @Benjamin Lellouche , have you attempted the new rule yet? If not please provide the details around "when some specifics tasks are "Done"...". Basically your rule will look something like this... trigger - issue transitioned condition - type = task condition - epic link = xxxx condition - status = done condition - ???…

Hi @Aykan Inal , I'm not sure I'm following you here. It seems like you want just a basic SLA I don't see what is unique about your request. I'm sure I'm missing something. Do you have an SLA set up now for time to resolution? If so, what about it is not working the way you want?

Hi @Andhika Pratama Wijaya , welcome to the community. I'm sorry, but I don't understand what you mean by the SLA Setting keeps refreshing. Can you describe exactly what is happening the image you show doesn't provide any clue as to the problem as far as I can tell. Are you in the project settings under SLA and seeing…

And no, I do not know of any alternative here.

Ah....I missed that you are on server. It may be different but a bit surprised that what I show is not supported there. Can you try build the automation I suggested? Maybe, just as a test replicate exactly?

Basically this but replace "Description" with your custom field.

You can take what I gave you before and simply make your action be to edit the field of the parent with the smartvalue that I showed in the log action.

Hi @Shamanth , welcome to the community. See if you can work the following into your rule. Please note that the last action is simply a means of logging the value for test purposes. I'm unsure exactly what your action plans are such as email.

Hi @Леонід Государський , that question might be best directed to Atlassian Support. and I found this page where, at the bottle, there is a link to raise a request with the internationalization team.

Congratulations @Brant Schroeder !! Well deserved and no you can't stop here...forward, always forward! 😉

I don't and would be surprised if there is one.

In JSM the ordering in the queue is driven by the filter and/or when you click on the column header. Priority or the order in which your agents work on issue will be driven by internal process and/or agreements in place with customers. For example... * you might treat all customers equally and then use SLAs or Priorties to…

Automation is a cool idea Charlie.

To be clear you want to find the issue ID and not the issue key, correct? The only two ways that I am aware of to acquire that information are: * via the export as you mentioned * via the API I found this post on the API - How-I-get-issue-id-of-particular-issue-in-Jira-Service-Desk neither of those is very user-friendly…

What drawing app are you using? Have you contacted their support? Have you tried different browsers? Maybe sharing some screenshots would help diagnosing what is going on.

Hi @Muhammad Amjad Ali , sorry I misread. I don't know of any way to setup your incoming as described OOTB. Maybe look at one of the two more advanced email handler addon apps if that is an option - jira-service-management:Email-handler 

Hi @Jameson Rader , First off welcome to the community. So I have seen odd issues from time to time in various browsers. In my opinion, this is not uncommon with software tools like this. The browser updates and or the application updates will conflict from time to time. However, they rarely last very long. That all is…

Indeed, Smart values is the way to include issue fields into your email. There are actually a ton of smart values that you can use. What exactly is missing? The format looks like this... for fields use ... {{issue.field name}} ... e.g. {{issue.due date}}, {{issue.assignee.name}} for the last comment use ...…

You cannot Use the same incoming email address for all projects. Each project requires its own unique email channel so that hey are directed to the proper project.

How do you identify an issues place in the queue? Assuming you have some method of controlling this then it might be possible to leverage Automation. However, I see a number of potential issues here. Please advise on my initial question and we can then see if there is any path forward.