Jack Brickey Expert

sort of painful but here is a thought... Assuming you have access to the original system: * query the old system to find some trace of the first and last issues imported, e.g. the summary field * search Jira to see if you can find the first and the last which would give you the two issue keys that could be used to identify…

you bet. TBH, i expect it will get buried in the many hundreds of open requests, many of which are undoubtedly higher priority or at least in higher demand. It will come down to how many votes it gets I expect. Assuming it makes it into the open suggestion queue at all. This is, of course, JMO. :-)

sure. just create two different workflows (note you cannot do this in next-gen projects in cloud). Have one workflow be associated w/ the single request type and the other WF associated to all other request types. Edit the WFs and edit the Create transitions, add a post function to set the assignee.

Not by default. When I have done this in the past I would always use bulk update and add a label, e.g. "imported". I also have created a custom field to include the previous systems issue-id. Maybe that was done?

Hi Brett, you might consider using the "Feedback" link w/in the application under your profile icon. Alternatively submit a suggestion via the Atlassian Support channel.

I really can't tell anything from the images. Regardless the only scenarios I have experienced where duplicates were created is this: * Customer A sends and email to the JSD projects email address and copies Customer B, C... ==> Ticket A created * JSD responds w/ an automated response..."we got your request..." * Customer…

unfortunately not. yes you will need to train them. i recommend against CC-ing anyone in initial requests. the user can add them after the ticket is opened. 

You are blazing new territory here. :-) I have not played w/ NG JSD as yet. But it is pretty clear that this feature isn't available which I find a bit odd TBH. I would direct you to Atlassian Support for this question. Please update here (in the form of an answer) when you get an answer as it will help future searchers.

see if this previous thread provides useful info for you - What-do-the-link-icons-in-next-gen-roadmap-mean if you are asking about linking the two using "Link" just go to one of the two issue and click on the link icon and enter the key to the other. 

You need to have the Jira Admin edit this I believe. Please check w/ them to see if they can. If not please have them contact Atlassian Support.

and add something like this as well... AND Resolution is Empty otherwise you will see all old closed issues

Ah. so you want your agents to use the 'portal' for creating issues? Your agents can and should use "Raise a request" link in the sidebar vs. the "+". Also any JSW users w/ permissions could create a JSD using the "+" if your permissions allow but that can be changed. However, you can't prevent Agents from using the "+"…

glad to assist!

pulling the discussion back into this thread.... I will NMI to assist. Here are some screenshots of how I have this set up. What mail server are you using?

not OOTB, reference this request - JSDCLOUD-3371 and vote/watch if desired. You will need to look at an addon like JEMH

What email settings? Are you referring to the email for handling email requests for JSD project? If you are an admin go to project > project settings > email requests.

Which product is unstable? If you are seeing an issue you should file a support request. I use A4J in cloud and while there are certainly some areas for improvement I have not found it to be unstable.

There isn’t any integration between A4J and SR. I wish their was. You might contact Codebarrel and inquire.

There is a new feature that allows you to ‘connect’ two epics to show dependence by clicking and dragging the link icon on the epic bar. You could also add one epic as a link to the other. I guess it depends on your linking goals if either work for you.

@Sebastián Delmastro , What exactly are you experiencing? How are you trying to remove the customer. Do you have the customer on other projects or just the one? Is the customer in an organization or at the root customer level?

Precisely. That was the purpose of my inquiry. 

Did you inspect the boards filter to verify the projects associated with the backlog?

Correct. JSD’s new issue view is different than JSW. What are you wanting to accomplish?

Ah yes, that is true. Off the top of my head I would suggest looking at an automation addon that could run daily or weekly. Search the community for recurring reminders.

This doesn’t appear to be from a Classic JSD project. Maybe this is a Next-gen JSD project? I have not spent any time with these templates.

Please review the above thread as the same responses will apply to you.

As others have noted here, the OOTB solution is to create a filter and setup a daily filter. The issue here is figuring out who to notify for the subscription. If the list of folks is small and relatively static this will work. However, if you want to notify the specific assignee you will need an addon. One option is…

You can certainly create issue within any Jira project by setting up an incoming email handler. Go to Jira settings > System > incoming email

I use the Time Reports for Jira Cloud there are other options in Marketplace

The fact that you have declared issuetype = story will exclude sub tasks.