Jack Brickey Expert

it can't be done in basic. the "!=" equates to "not equal to" so it is not associated w/ empty. in advanced.. IS EMPTY IS NOT EMPTY

i would inspect the logs to see if there are any clues. also i would check what is shown under the system admin area for user management and inspect the portal only customers.

If it were me I would simply create a filter called Triage that equates to... project = myproject and issuetype = bug and assignee is empty then I would use the filter to triage each issue and set the assignee which makes it fall off the Triage list. In other words, triaging requires you to set the assignee. Alternatively,…

you could consider an addon like Automation for Jira.

it has been confirmed as a bug - JSWCLOUD-18136

isn't that annoying. :-( it cannot be changed or I have found no way of doing so.

in the project you should see Customers in the sidebar

check the customer notifications under project settings to ensure it is enabled for the specific event.

if you have the project setup to allow customer to join simply by sending in an email then this could be the cause. you can elect to restrict customer to only those added by your agents. 

having redundant customers listed there is not possible. You might have the same name but the underlying email will be different. if you want to remove them then remove from the Customers list in the project.

do you have invitation notifications enabled? project settings > customer notifications ... Customer Invited should be enabled.

bad link

Sarah as I mentioned previously your images are not showing so i cannot comment on what you are are seeing. The URL was specifically to the one gadget (sprint burn down as can be seen in the URL. You might get a quicker resolution going directly to Atlassian Support.

@[deleted] , let's keep the replies under the original answer thread.

I have not attempted this myself TBH so it may be a bug/limitation. You might want to reach out to Atlassian Support on this. If I get time later today I will run a test.

Shawn, this is an old post and things have changed since then. Can you elaborate on exactly what issue you are having and what you want to happen?

Try the Alert function rather than send email.

I suspect this is related to recent changes associated with GDPR. Please contact Atlassian Support so they can log into your instance and inspect.

What widgets? Can you please add more details so that the Community might be able to assist.

The details of the templates tend to change so I can’t give you a side-by-side comparison. There may be something in the documentation so you may wish to look there as well. With that said the main difference I have found is in the workflows. The external one, usually is more involved and includes the concept of the…

Jira has the notion of watchers. If the colleagues are users in your Jira instance you can add them as watchers. JSD has the notion of Customers that do not require a license and can be added as Request Participants which are similar to Watchers but the difference here is license vs. no license.

Are the issues that are not showing in these sprints ever showing in the backlog? If not then the cause is that the board filter is excluding them altogether. The normal process is to drag issues from backlog up to a planned sprint vs. setting the sprint manually. I am suspicious that the sprint name being filled in…

Did you happen to try a different browser as well? If it fails there and is persistent I would reach out to Atlassian Support as this seems like a bug to me.

Ha...and it all seems so obvious in the end. ;-) glad to assist.

if on cloud the url will be something like urcompany.atlassian.net the sprint burndown URL is -https://urcompany.atlassian.net/rest/gadgets/1.0/g/com.pyxis.greenhopper.jira:greenhopper-gadget-sprint-burndown/gadgets/greenhopper-sprint-burndown.xml replace "urcompany" with your atlassian URL company.

yes indeed. I use the "." frequently.

I can't say for sure given everything is green but here is what I would do to troubleshoot. Basically, I would want to start simple and layer in the conditions. To that end, progressively change your automation as follows: * When Comment added Then Transition * When Comment added AND Status = W4S Then Transition * When…

Based upon what criteria? Do you want every issuetype of "Bug" to always have the same label? That seems sort of redundant given "bug" is a label for all intents. That said, you could consider an automation addon to add the label. Updated... One possible OOTB solution would be to create a custom field "bug-label" and set…

Ah...so I now see. it is the Agile Wallboard Gadget. I just played with it and indeed is coming across as blank. I will continue to look at it but my first impression is that this is a bug and will require reporting to Atlassian Support. I opened a support request.

i'm intrigued. what is the gadget called exactly. i'm not immediately seeing it in my cloud instance.