Jack Brickey Expert

agree that seems to be the smoking gun

@Bridget Sauer 

At first glance nothing is standing out for me. I would consider simplifying the goals to troubleshoot if possible. Such as... remove organization condition and test remove issuetype and test check that issues are getting assigned for your second sla

Something about the subject tends to tell me the replies are not occurring cleanly. Specifically the reply has “re: future ticketing help :” where does that originate. I would expect the reply to simply be “Ftserviced...”. i wonder if there is another email reply going on or the customer is editing the subject which may be…

* Create a “team” field with a single-select * leave “unassigned” to equate to triage * setup filters and dashboard if desired or even Kanban per team that leverages the team field 

More details on this... assignee based upon component only happens at the Create transition if component is set during create. Options: * JSD has OOTB automation that can be used * JSW requires an addon, e.g.scriptrunner, Power Scripts, Automation for Jira, etc

Just an opinion as I don’t really know how you company works but maybe this... Brands = projects components = website, SEO, ads..... another thought... Brands = new custom field and use for swimlanes components = website, SEO, ads.....

I think you are speaking about the breadcrumbs that are normally at the top. This is was a regression with a recent update in cloud. It has bee addressed and is being rolled out. You might wish to reach out to Atlassian Support to ask that your instance be updated.

When you go to Jira settings > issues > custom fields > add custom field you will be presented with the basic (and supported) custom field types. If you click Advanced you will see the toolkit additions (unsupported)

I believe that is a function of Portfolio. Do you have that product?

Hmmm, so you are saying the reporter is replying to the email sent by JSD notifying of the ticket creation and a new ticket is created? Do you have any email addons?

Check if others can create projects. If so ask your admin to verify your permissions.

Agree with joe on the resolution part. I would also suggest you try a simple experiment. run these two filters and compare them for Any overlap as there should be none. project = efm and issuetype = incident and status = created project = efm and issuetype = incident and status = closed if you any overlap I would be…

ok so there is a lot here Josh much of it is just coming up to speed w/ JSD and I think the docs and diving in will ultimately help the most. that said let me try to help... * Queues - Absolutely you can do this. How you do it depends on how you setup Incident, request, changes. Are these already setup in the project? If…

you might wish to contact Atlassian Support directly for this issue. unless you did and were directed here is which case you have a starter license meaning the Community is your support forum.

Hi Josh and welcome to the Community. I haven't personally use SN so cannot comment on the comparison. However, I can try to answer some of your JSD questions. When you create a project in JSD you have a few template options one of which is focused on IT. The main differences between the templates are the workflows and a…

also reference their Known Limitations do convey that not all custom fields are support so I'm not betting checkbox is one of those not supported. :-(

Hi Bernadette, I am also evaluating Refined at the moment but have not looked into whether checkboxes have an issue or not. That would seem odd for sure as my view of Refined is simply an overlay for JSD and as such should not compromise field presensation. I would recommend contacting Refined Support to get there input.…

First some terminology: Dashboards are independent views that leverage various gadgets to provide overview of various projects, issues, etc. while Board’s (Kanban, Scrum) In business projects you only get the Default (non-configurable) board. This is what you are seeing in your current project view. As I mention above you…

Do you have the necessary Manage Sprints permissions? 

Have you verified that you have the necessary Assign issue permissions? Can you assign issue from the detail issue view?

Has this ever worked for you in this project? I am wondering if you have the necessary Create permissions. can you create an issue in the project in question using the “+” on the main sidebar? Is this a Next-gen project or classic?

Note you don’t create admin accounts you add users to the admin role. You must be an admin to add another user to the admin role.

Who is listed as the reporter? Is it a user or some system user? Start research there and then expand to other breadcrumbs the issues might yield. feel free to offer us an image if you wish.

You can change the Reporter, but maybe you are looking for more than that?

My first theory would be someone has set up some automation or script to create issues based upon some trigger or schedule.

The issue has been rolled out to my instance and expect it has been or will be for all soon.

But isn’t that image showing the default board? At least that is what I call it. What do you mean by default board? You may already be aware but let me state the following just in case it is helpful... * you are in a business project as such the default board (shown) is what comes with that project type * you can create a…

I wish I could help but there just is too little info here. That said I’m pretty confident that there is a logical explanation vs. some anomaly. If you can reproduce then we can troubleshoot more.

I moved the post to JSD collection. now to your question, does my previous answer give you what you wanted? That is your customers need to use the portal to view issues.