Jack Brickey Expert

Yep and the advantage of this approach is you hit a target audience per issue. The subscription hits a broad audience which would include issues where an approver may not be interested.

Consider using a filter and subscription. If you need assistance in this please let me know. 

Let’s focus on the word Dashboard here. What gadget in your dashboard is doing this? Can you share an image that depicts the issue? If you use Advanced search what do the results convey?

so it sounds like those are Request types. Please confirm under project settings > request types. Assuming so, and assuming you simply want all email requests to result in Incident rather than Queue the go to project settings > email requests and click on the ellipses in upper right corner. Select Configure email requests.

You can create and save a filter using JQL (click in the search and advanced search). Once you save it you can set up a subscription to run the report on a give schedule and include various parties.

So what defines an "incident" here? Is Incident associated w/ Opsgenie or is Incident a Request type or is Incident an Issuetype? What ends up in a Queue is defined by the underlying JQL for the queue. Email requests in JSM are associated to a specific Request type.

yep and please do as this is ugly stuff. i hate it but also understand it. many these days uses images in their signatures which wrecks havoc on sw systems like this.

I'm sure i'm overlooking something. It sounds like you want this: hide sub-tasks in the backlog but display them once their parent moves into the kanban. For this I would use a QF in the backlog to hide them... "Hide Sub-tasks" --> type != sub-task if you happen to have some other statuses mapped to the backlog and you…

are you just trying not to include the sub-tasks in the backlog? If so why not change the board filter. If you may want to see them at some point consider quick filter.

it is in there. it didn't go thru initially but you should see it now. LMK.

Hi Pankaj, this would be (i think) associated with how the workflow was set up. Awaiting Resubmission is a status in the workflow. It may be that it is either the initial status where all issues of that type land (unlikely) or it may be there is some automation involved that is transitioning the status to this status…

Hi Erik, welcome to the Community. There are various reasons why emails may not result in issues being created. Can you go to project settings > email requests and click on the view logs for the specific email channel that is involved here? Do you see any failures? If so what is the error?

@Ankita Chattopadhyay , were you able to achieve you goal? Can i be of further assistance?

So the trickiest part here is the Component restriction requirement. I will refer you to another thread here as it does a good job of explaining things. Basically you need to employee issue security. 

Agree. Jira would be a very poor choice for doc repository. Consider Confluence, Sharepoint or other tool designed for the specific task. 

Well, my answer has always been that for the incoming email to be considered a comment then the issue key must be in the subject line. With that said, in a very recent test using Gmail I found that if I, as a customer, replied to my original request it actually updated the ticket which shattered all previous laws of…

In a word - No. There are a lot of posts in the Community and I recommend you use the search bar to seek these discussions out. Basically, Jira is designed to have single accountability for issues which doesn't work well when you assign a single issue to a team. Rather break the task into subtasks and assign to…

Hola Francisca, Si el tipo de problema es incorrecto, utilice la función Mover y luego edite el Tipo de solicitud del cliente. Si solo el tipo de solicitud es incorrecto, entonces debería poder cambiarlo directamente en la pantalla de vista detallada del problema

why would you not use Move to move the mis-placed issue to the correct issue type?

There aren’t email addresses associated with projects. However you can create email handlers for a project for the purpose of creating issue by email. Is that your goal? If so go to support.atlassian.com, choose Jira as the product the documentation and search for creating issues by email. 

The best solutions include well named Request types. For example: Phone issues, Computer Issues, New hire setup, Printer issue, Feature request, Software bug, etc Couple this with very clear descriptions. 

Wo hören Sie von 1-Klick. es existiert nicht. Ich bin mir nicht sicher, wie ein 1-Klick funktionieren würde. Sie müssen mehrere Themen auswählen. Sie müssen eine Aktion auswählen und ausführen. Selbst wenn es eine andere Lösung gäbe, wäre es kein Klick. Sie können eine manuelle Automatisierung dafür selbst definieren. Dies…

Thinks for the explanation. I don’t use X-ray. Hopefully, someone that does can assist you here. good luck!

Sie können die Massenbearbeitung verwenden. Obwohl es nicht "ein Klick" ist, sind es mit Sicherheit weniger Klicks. Gehen Sie einfach zur erweiterten Suche nach Problemen und geben Sie die JQL-Suche ein, die die Probleme definiert, die Sie bearbeiten möchten. Klicken Sie dann auf die Ellipsen und wählen Sie…

Please explain “cucumber scenario”. Also are you using some test management addon here?

Hi Chee, those appear to be Epics. Epics are special issuetypes that are used as ‘containers’ for other issues. They typically capture a long term effort to achieve a set of related goals. You create these just as you do other issues cost the Create button but you give it an Epic name. Then you associate other issues to…

You can create a new screen under admin > issues > screens. Then to associate to the transition just double click the transition when editing the WF. You will see the screen files where you can select the created screen. 

yes. not AFAIK. That said, Roadmaps are new (for classic anyway) and as such I have not used very much.

For me Story is a unique way of describing work and should adhere to the following summary format. As a xxx-user I would like to be able to do yyy It is an expressive way of describing in conversational language the desired outcome. Stories focus on who the change is for and often express the why in the details. The…

no contest....the "/" shortcut...oh or maybe the table editor...errrr the info/note/warning/success panels... :-)