Jack Brickey Expert

Only on the detailed issue view in the portal, not the list view. However, I have seen that they are working on allowing us to configure the fields in the portal so hopefully in the not too distant future this will be possible.

Hi Igor, can you check the filter share? Board settings > General. Ensure that the filter defining the board is shared with others.

Hi Poppy, welcome to the Community. I get the frustration for sure but I’m betting we can get back up and running here. A couple of thoughts on what may have happened but there is a bet of guessing on my part until I have more data. You indicated that all your issues were in the Backlog until you updated the Epics. So how…

Someone (admin) added the "impact criteria" custom field as required. Please reach out to your admin and have them inspect what was done vs. what was intended.

please keep us posted.

well that is sure odd. I can't provide guidance beyond a) try another browser (expect same result), b) log out and back in and retry, c) contact Support.

Hi Carol, welcome to the Community. So I still see "manage rules". So maybe you are on a newer update than mine and either they have actually introduced workflows (yay) or simply changed the name. What else do you see when you "manage workflow"?

POC?

but this is JSD where Organization is an actual thing.

there is this article - migrate-between-next-gen-and-classic-projects basically, you would: * create the NG project to receive the issues * create a filter (JQL) to display all issue to be moved to the NG project * Use Bulk edit * select the Move option

there is not a "create" or "add" to sprint capability OOTB. I think the reason is that you really shouldn't do that or at least make it a habit so don't make it easy. Just my interpretations of this. You can obviously add to a sprint from Backlog or directly from detailed issue view or the Create button.

If this is reproducible on different browsers at will I suggest reaching out to Atlassian Support. Note: i found this issue in JAC but it is different - JRACLOUD-72753 

sorry..... No you cannot do that. If they are in the same org and you have the org in multiple projects then they are part of the projects where the org exists. Now note that unless you have "organization added" enabled under Customer notifications then user B won't be notified when user A creates an issue. However, if…

Hi Olha, welcome to the Community. I was playing around with this and actually ended up reaching out to Support because what I found was with the new Issue View you can't actually display the Epic Status on the detailed issue view. This is most unfortunate for sure. There is a Bug (now closed) that reported neither the…

This is precisely how Jira service desk works. If you are talking about customers then you simply add the customers you want to have access to the given project and the same thing applies for service desk agents you add the agents you wish to have access to each project. 

A team is really just a concept in Jira. There isn’t an actual team that you create and label as a team. Often team defines those users that have permissions in a project.

I just did a quick test and I don’t see the Share button. Have you tried this and are seeing it?

I have not heard that. Could you share your source. Assuming this were true I don’t believe anyone in the Community would have the answer as to when unless it was in fact public info already.

Not that I’m aware of and would not expect that to be the case.

I will move this to discussions since there really isn’t a question here. One consideration is Data Center.

If you have the first option ticked under project settings > customer permissions > who can customers share with AND you do not use organizations then there will be no sharing.

@Siraj Berry is there some specific concern that the Community might help you with? There are certainly many questions and good answers in the Community.

I recommend researching the Marketplace. Here is one option I found with a quick search - ezee-worklog 

Wouldn’t you just use the Cascading select field?

This is precisely how JSD works where issues created/updated are concerned. Each project has its own incoming email.

there are no gadgets (AFAIK) that allow for direct input.

Yes. There are a couple of ways to do this. Easy Way - if your current monitoring SW can issue an email when the abnormal condition occurs then you can set up an incoming mail handler to create an issue. The one thing to consider is that if your monitoring SW does not have any sort of de-dup capabilities then you could end…

It is worth updating here that this issue - JSDCLOUD-4580 is actually seeing some traction from Atlassian development. We shall see what comes of this activity in time.

Yep - Standard vs. Premium

Yes but let’s state it differently. When creating Request types you must associate it with a single Issue type. This allows you to present meaningful types to a customer while having a single workflow, scheme for multiple RT.