Jack Brickey Expert

Here is something you might play with. * create a filter like - project is not empty or maybe Fix versions is not empty. Save it and name it * create a dashboard with a 2-D gadget and set x-axis to project and y-axis to fix versions not sure this will be a pretty view but worth a shot. Flip the x/y if it makes sense.

With NG the RHMC is the only done category status and the only one green. I would definitely clean this up and not have the archived. 

Oh wait sorry....this is NG. Didn’t focus on the title. :-( I don’t use NG much at all but don’t believe you can.

If you expose the Epic Link in the issue create screen you should be able to add the epic at that time. Is this not working?

There isn't anything like this in Jira.

assuming you are speaking of the OOTB automation you can choose the project default of user who triggered. project settings > Automation find the automation in question select and edit click on the gear icon change to user who triggered

FWIW, i would not change the filter. Rather I would address the issue thru the Resolution field. All issues that move to an Done category statuses should include setting the Resolution. This can be done by exposing a screen on the transitions to all Done category statuses OR via a Post Function to set the Resolution by…

I think the issue is that you are not setting the Resolution field when issues are moved to Closed (or whatever your terminal state is).

Please share your board filter. "OBE"? Closed issues most certainly should not be on the backlog.

I should have mentioned that the aging is for NG Kanban. NG Scrum will remove all issues from the board when you complete the sprint. I'm guessing you are using Kanban though. Now can you look at one of these old issues and see if there is a Resolution set as in below... If you are not seeing the resolution then that would…

this feature does not exist unfortunately. there may be something in the Marketplace for this but TBH I am not aware of such. I would imagine the reliability of such in the current implementation would be questionable. For example If a user has a browser tab open to a specific detailed issue view that doesn't mean they are…

make sure he has Manage Sprint permissions for ES and TPM in addition to SC.

the way NG boards work, unless something has changed, is the issue in the far-right-most column will age off after 14d. You want the FRMC to equate to "really done" work as in we won't be spending any more time on this issue. Anything to the left will fall into pending work (To Do which should be the left-most column…

So I created a filter - resolution is empty which returns ~1500 issues in my entire instance. I created a Kanban and while a wee bit sluggish it actually works fine. Now one key difference is that this is not single project and is certainly not a NG project. While I do have a handful of NG issues in that filter they are…

800 issues on a board is quite a lot TBH. I am not saying that should equate to the sluggishness just that from a manageability perspective that seems excessive. I'm going to run a couple of test on my instance by fashioning a board that has 1k issues and will report back what I see. In the end you may have to reach out to…

Agree that exporting the data is the first step. Keep in mind that Azure is just an IaaS (bunch of servers where VMs are setup to run applications). In an of itself Azure is not an application for storing issues. It may be that someone in your company has created a home-grown solution sitting atop an SQL DB. I would check…

could you share a screenshot so I can better assess what you are referring to?

I am not familiar with a "Program". Maybe this is something unique to Server or maybe this is associated w/ an addon or maybe Portfolio? Can you elaborate? You can certainly filter on a project in Jira (project = myproject....)

* If a user sends an email to the JSD email then an issue will be created. * If a user replies to a notification email that is sent from JSD then a comment is added. * If someone was CCed in the original email to create an issue and that person replies to all (which includes the JSD email) then a new issue is created. why:…

The email you reference under Email requests is for incoming to create tickets. Cloud uses a default outgoing (yourcompany@atlassian.net) and this cannot be changed. You can consider an addon mail handler app to replace the built in mail handler. You can vote/watch this issue -JSDCLOUD-2075 

good to know. a bug explains this one best for sure. ;-)

but what application are you exporting from? what is currently running in Azure that you are migrating away from. If you can figure out how to export all of the info you need from Azure into a CSV then you can use it to import into your Jira Cloud instance. See this article - creating-issues-using-the-csv-importer 

Hmmm, if you have the field configured in the Create Screen for the project/issuetype then it should remain. Check the screens for the project (project settings > screens) and be sure to review each issuetype/screen to ensure it is indeed listed.

Hi Jonathan, can you elaborate? You mention Azure, are you saying you currently have a Server instance of Jira stood up in Azure and you are looking to migrate to Atlassian's On Demand cloud solution? If so you may find this site of interest - Cloud Migration Center 

you can create a Group and share the Dashboard only w/ the group. However, if the group is going to be dynamic that can be cumbersome. You can't share based upon assignee dynamically.

Hi Chris and welcome to the Community! As explained this surely seems odd but let's dig in a bit. What issues don't carry into Sprint B initially? Are they unfinished Sprint A issues, Sprint B only issues or a mixture? To be clear just prior to starting sprint B you have say 10 issues (7 SB only issues and 3 SA&B issues)…

you may have a To Do column on the Kanban board but what status is mapped to it? It will be different that the status that is in the Backlog section of your Backlog board. As Avinash suggested share your filter and more info about your boards status-column mapping.

thanks for sharing. Chrome might be an interesting solution but I don't use Chrome. My experience w/ it is less than ideal performance-wise. I was not familar w/ the the Images field that Tarun spoke about but gave it a try and agree it isn't very useful. While you can mouse-over the image and the full image pops up…

no problem glad to help. If you get any info from Atlassian that you think would be useful to others please include here. Cheers!

Hi @[deleted] , to be clear I do not work for Atlassian. I'm a user/customer like yourself. Given you have 12,376 issues this will require 13 exports. Yes tedious but not horrendous, maybe 30m of work at most. Here is more info on how this is done along w/ background - export-over-1000-results-to-excel-from-jira-cloud .…