Jack Brickey Expert

Hi Cristina, I don't see any practical solution for this. How would you force such behavior? Even if the solution required them to click on a KB article there would be no way to force them to read it.

Have you considered using Components to assign? Also look at Automation coupled w/ a field setting that 'defines' project team.

You may want to look at Portfolio application. You could also consider a simpler solution of using labels for Features.

If you set up a project for anonymous then it will show on the Help Center, this cannot be changed. If the project is restricted to login the it will only show for the specific customers defined in the project.

Thanks. I would suggest removing and add back the email. I would also suggest disabling password expiration in outlook for this account.

Oliver, you reference an article for Jira Software but mention Jira Service Desk here. Can you clarify which application you are inquiring about? If JSD, realize you set up for email requests within the project > project settings > email requests. It is different than setting up incoming email handler in Jira SW.

ah yes that is correct. I don't think this can be done by JQL. You may have to create a listener and capture the approver in a custom field.

You simply need to create a filter search and add Approvers to the column list.

No problem. Note that this method will remove them from all JSD projects. If you only want to remove them from a single project then do that within the project(s).

Yes that will do the trick.

By design NG projects are independent islands; every field is unique to the project it is created in. Given your requirements I would choose Classic projects.

The only addon not available in your list is nfeed aka Elements Connect. I am not familiar with the addon in detail. Have you searched the Marketplace for alternatives? What exactly do you use the addon for?

You are most welcome.

Not OOTB unfortunately. I was just discussing a related topic with Atlassian Support and here is an excerpt that is relevant to your question. Unfortunately, it's not possible to natively remove images/signatures from inbound emails as documented in various forms here: * JSDCLOUD-2090 - Be able to remove images in mail…

Have you verified that the individuals you are trying to mention have access permissions to the project, either as an agent or collaborator.

They could only accomplish this by doing the math - created date/time - resolved date/time.

SLAs are intended for agents only not customers. If you want to share the SLA goals you could use the Knowledge base article feature.

you will need to reach out the the admin to help with this as you apparently don't have the necessary permissions.

this is not possible. the only view a "customer" has is the portal.

you can use Bulk edit. once you have your search query producing the issues you wish to update you can then choose bulk change from the ellipses drop down in the top right hand corner.

you can edit the filter used by the gadget and exclude "irrelevant" sub-category. if you own the board of course. * click the ellipses and edit to find the filter * go to the filter and add... and "sub-category" != Irrelevant * save the filter and you should be good to go

I use Automation for Jira and set up a scheduled event to trigger it.

I would check for any automation that might be the culprit. I would need more info to assist further. Are these exact duplicates? Are you accessing thru Jira UI to create the epic or thru and API? 

agree this is strange... have you scrutinized the two that do not show? I wonder if they are closed and reopened (again) would they show. however, if they did show, that wouldn't answer the question of "why".

you need to be sure to clear the Resolution field when reopening an issue. Do this with the post-function.

If they leave you don’t need to unlink you just need to “revoke access” them altogether under the user management in Jira settings.

Maybe sharing the actual automation would help us troubleshoot.

While I use NG projects in a limited capacity I do not know of any way to do this.

not sure what you mean by merge request types. Request types are associated to Issuetypes and is simply a way to add common language to issuetypes. Too it allows you to group requests under common workflows, schemes, etc. request types do not have to have different workflows. In fact every request type could share a single…

No. Roadmap is based off of the epic issuetype.