Jack Brickey Expert

Project = xxxx and duedate is empty and assignee = currentuser()

You can’t get that from JQL. I found this addon that might give you just what you want but I have no experience with it - gauge-gadget Finally, you may be able to use Automation with a custom field that would increment the field ever time a link is added to an issue.

Maybe you could use Issue updated as trigger and JQL as condition?

Not necessarily. When a user logs work they have the opportunity to set the remaining time. So a user could have logged 1.5h and set remaining time to 30m. Please check the Work log details under the Activity area.

I found this server doc that specifies the limit as 2147483647 characters. I did not find in cloud docs based on quick look but likely the same.

This is where Atlassian documentation comes in handy. Depending on the details surrounding your question you would want to inspect one or more articles. Here is a query for “releases” in the cloud docs - https://confluence.atlassian.com/search/?productName=Jira%20Software&productVersion=Cloud&queryString=Releases 

Could be permissions, workflow issues, bad config... please provide more info so that we might zero in on the issue. Q - next-gen or Classic? Q - do you have admin permissions such that you can inspect the workflow? Q - what is the story board in your question?

jira-server-for-slack-official jira-server-for-slack-official-versions - the latest version addressed a vulnerability on Jan 22.

You could use the smart values and the diff operator. For example.if you create a rule that triggers on issue closure then use - {{now.diff(issue.created).days}} and stuff that result into a number custom field. Give it a try and use the “log action” to record the result and then inspect in the rule audit log. Once your…

Ok so maybe your “services” are “Request Types” in the project? If that is the case then you can certainly define your SLA goals by RT using the JQL in the goals - how-is-jql-used-to-create-sla-goals example... 4h - “customer request type” in (service1, service3) 2h - “customer request type” in (service2, service5)

Your url can be copied from your browser it should look like this... https://xxxxxx.atlassian.net 

Based on your original post I would suggest the one I indicated in my image. Ultimately it depends on your process. For example if your team works on sub-tasks if they exist and not the parent then you could auto close the parent story when all sub-tasks are done using Automation and similarly close the Epic once all…

How are these services manifested within JSM? SLAs are associated with issues in JSM so if these services can be associated to issues then yes, if not then no.

Service category? Please explain.

you could certainly add a custom date field and use Automation to set the Epic Status to DONE and the custom date field when all underlying issues are resolved. there is an automation rule in the library for closing the Epic when all issues are done. You could use this and add the action to set the date field.

So I see a lot of config change entries but nothing after. I need to see a trigger and then expand the log.the last trigger at 3:53:47 shows no actions performed. Can you cause the rule to trigger and expand the log?

ah... i have been meaning to tune into that and see what it is all about. Tonight might be the night!

to be honest I have no idea. Can you tell me which addons you have. With that I could inspect the Marketplace and see if any strike me as a possibility. Now it may not be an addon but I cannot understand how you would have a locked field otherwise. IMO, I cannot imagine why an addon vendor would use a field that is already…

if you are a Mac user there is a client that supports DM.

i'm not quite following as to what transpired however, lets investigate the automation in place. So if I understand you have the above automation enabled for a specific project correct? But the automation is failing, correct? What do the logs tell you? Can you share an image of the logs? I suspect they will convey where…

I don't understand the question. Are you asking for all of the default system fields? Realize you can add custom fields which would make providing an accurate answer here impossible. Maybe you can articulate what you are trying to accomplish or maybe reviewing the documentation would be a good place to start? 

Hi Gabriel, I believe this is only available to Community Leaders and I should have mentioned that. The reason is, that we don't want Slack to replace the Community but it gives the leaders another outlet to discuss CL activities and support each other in our support for the larger Community.

ok so we are overlooking something totally basic here or there is a very weird bug. I'm placing my bet on the former. Do me a favor an remove your sub-filter and change your hide completed issues to never hide.

sorry, not following. If you set the project up to add the person as a customer then they will get notifications in accordance w/ your Customer notification config.

glad to assist in anyway I can. if you need any JQL assistance at all JLMK! cheers!

that will only work if the user is a customer OR you have the project setup to add new customers when they email in. Otherwise the JSM email handler will block it which can be observed in the email log as "Failed",

test project? Ha I laugh in the face of test projects. Damn the torpedoes. Full speed ahead! ;-)

you could have a look at building an Automation rule. I would think you would want to consider some careful Conditions to ensure linked issues do not get closed except for the specific case you desire. In any event play with it and if you get stuck come back here to discuss if you like.

no problem at all! Here is a doc to start with - advanced-search-reference-jql-functions . However, I don't think you need to even use the advanced JQL for your purposes. Rather stick w/ the basic search method - perform-a-basic-search . In Basic search you will have drop down options to build your query. Advanced will be…

well server sure makes more sense. I was going down the wrong path.