Jack Brickey Expert

Sorry I can’t help you on this directly as I have not attempted myself.

I’m sure there are quite a few you could consider. Basically a scripting addon, e.g Scriptrunner, Power Scripts.

Correct

My advice is to indeed do backups. We auto backup every few days and store our backup in our own cloud environment. From what I understand, Atlassian performs their own server back ups which can be use for catastrophic failures not at an individual customer data basis. Disclaimer, I do not work for Atlassian so cannot…

You might consider moving to Premium which introduces advanced roadmaps (formerly Portfolio).

Can you share the config shown at project settings > customer permissions? Also, share the results from project settings > email requests, click on ellipses and select manage allow lists.

If you have “any logged in user” in any project then it will do just as it says - allow any logged in user the specific permission. there is a lot of existing posts on this in the Community. Here is one that does a good job of answering this question IMO - JIRA-Software-project-permission-restrict-user-access-to-one 

What role are you in? If you are a customer it should work without additional configuration. If you are in another role please check project settings > permissions > add comments.

What I was trying to suggest is that you have a drop down that represents your teams. You don’t create teams. In fact you could use Components as an example. As a demonstration let’s take a SW product that needed support, you might have: UI, Backend, Platform, OS, etc. now if you simply have a single team then you don’t…

Yes, adding a linked issue is almost always the way to go. Use the Create linked issue feature.

So next-gen boards do not allow for configuration of the cards. This feature is only again Classic projects. You could could migrate to Classic if you really wish but it is very different and not always a painless process. If you are not deep into the NG project you could simply create a classic and start over.

You should set resolution when going to terminal state but must also clear if you exit/reopen.

So can you go to one of the issues (or the issue) and click on the automations section to see if you can manually run?

I assume that the 2 tickets in “your work” are also in “assignee = currentuser() and resolution is empty” or are the two completely different? Moreover which list gives you the result you want or would expect? lets say you expected the 3 tickets but are only seeing 2 of the three. My expectation is that the 3rd issue is…

I wonder if you are on Next-gen project. Bottom left corner would state that if it is the case.

It depends on the automation. What is your trigger?

I’m not suggesting you change your workflow. I believe that the reason that the issue is not showing under your work is that it has a value in resolution field. Can you confirm that? My understanding is that “your work” is defined as follows (Basically if not precisely) assignee = currentuser() AND resolution is empty if…

It should be. Are you able to navigate to Board settings? Upper right ellipses.

it sounds like maybe an automation is kicking in here and that automation is being run under the specific user's name. Can you check that possibility?

if the resolution is set then it won't show in Your work. Resolution should only (always IMO) be set when an issue is complete. would this explain what you are seeing?

Sorry Lindsay, I just assumed you were aware of screens and how to configure. You do not need to delete any custom fields. Basically, you can create screens and associate to an issuetype in a project here - project settings > Screens. In there you can either edit the current screen scheme or associate a new scheme under…

they should be there. but be sure the resolution isn't set on these issues. what shows if you use these JQLs: assignee = currentuser() and resolution is empty assignee = currentuser() and statuscategory != done

we use Epics more for sub-projects in our world than features. Features works well (sort of) in the SW world but not so much for business projects. so optional will be best for sure.

I know of no concept of Feature in Jira. You have Epics, Stories, Tasks, Sub-tasks. Where are you reading info on feature and depreciation?

Quite different. Automation is built into Cloud and it does not require any scripting. Basically it is a lego like automation tool where you select various options and populate conditions, values, etc. if you give it a quick try I think you will find it intuitive. Project settings > Automation

please keep us posted on final result. probably something basic we are overlooking.

you should use "Raise a request" not "Create" if you use Create you must set Reporter AND the Request Type

theory... i think the issue is that the assignee is still empty when it hits the email leg. I think until the automation is fully executed the assignee isn't complete. test... separate the automation into two rules: assign, then email the second triggered by the first.

sorry scratching my head. i would really need to see this in person to troubleshoot. if others here don't get you sorted out I recommend Atlassian Support as they can log in an have a look.

the link for an issue will be specific to the project not the main Help Center URL. If the customer isn't able to access the project then they don't have access to the project, i.e. they are not listed as a customer in the project. you cannot change the portal url as they are project specific.