Jack Brickey Expert

Consider using Automation for Jira or similar. Use a unique status and when the agent transitions the issue to that status the linked issue is created. You cannot display the linked issue on the portal and even if you could the customer would not be able to access unless they were a user in JSW.

You can certainly create issue by email. It has nothing to do with the mail client but you need to get the right port, etc. You need to create a email handlers for each project where you wish to create issues. Here is an article that may help - creating-issues-and-comments-from-email 

Is your ‘final’ status “Done” if not please use the name of your status. 

The only options are to live with the limitation of NG or create a new Classic project, move all issues over. You should be able to do so with little disruptions to your customer. You can do during down time and remove the old portal project and replace with new using similar or same name and email.

So you have you attempted to create a cascading custom field and then associate it to your JSD project? Custom fields is part of Core so you should be able to add to any project type, with the exception of Next-gen.

If a user has edit permissions they can add and delete labels. There is no separate Labels permission.

I have never experienced them not being sent if enabled. I would check junk mail just to be sure. If you are confident they are not being sent then I would contact Atlassian Support.

You can’t find issues moved using JQL but you can with an addon like Scriptrunner. Here is a previous post that provides the necessary script for this - How-to-find-issues-that-were-moved-from-one-project-to-another 

Here is an idea to explore using an addon like Automation for Jira... create a custom field in JSD project and when the Assignee is updated in the JSW linked issue then copy the user to the custom field.

Check the following - Project settings > satisfaction settings is it enabled?

I suggest the following: * create a custom user picker field called say “FixedBy” or whatever * on the transition from In Progress to In QA add a past function to copy field Assignee to FixedBy * on your reopen transitions use PF to copy field from FixedBy to Assignee

You could create your new project using the desired template and then perform a bulk move of all issues to the new project.

Not surprised. You likely have a single screen. You can certainly add Epic Name to this screen. The only downside is that you will have Epic Name shown on the create for all issue types which is fine but if you want you can create a uniques screen and screen scheme.

You need to go to Project settings > Screens and add it to the create screen for Epics

You can see this in the detailed issue view of a single issue. 

If you want to copy then use the Clone feature under the ellipses in the top right corner. If you want to move them to another project then use the Move feature in the same location. 

Exactly my point. You never know what version you are on but it will be recent whether it is latest or not.

Project settings > features and toggle sprint off

you could run this filter project = xxx and status = done this will return all done issue but it will include those still on the board.

welllllll....not always. :-) Atlassian is constantly rolling out new versions but there will be many different versions running at any moment. for addon version go to Jira settings > Apps > Manage apps > expand the app in question and look for version.

What I mean is that you can create a filter, save it and set up a subscription to run daily/weekly, etc.

@kunle.kuteyi, unsure why you accepted this as an answer. Did you resolve your issue? If so would you mind documenting what the solution was?

no worries. so do you need further help on this? I think what you are going to want to do here is to edit your workflow and not allow an issue to transition to Done without going thru the QA status first. That is, the only transition to done is thru QA. Now that might be too restrictive since there are times that an issue…

I have never seen that popup w/o cause. That is, if you are a system admin you can login as another user which is quite useful for testing things out as a user vs. as an admin since things appear different when you are an admin. After logging in as a user if you have any other Jira screens open then they will pop up that…

Sorry Lindsay, that was rather cryptic :-( So what I do is I have a Triage queue(s) for unassigned issues. All issues initially come in unassigned. It is up to my entire IT team to monitor this queue and keep that queue empty by taking ownership or assigning ownership to one of the other agents. This is particularly useful…

Unfortunately that is not available. you only get the parent task/story of the sub-task in the breadcrumbs.

Hi @[deleted] , welcome to the Community! Are the issues perhaps showing in the Backlog? Issues will only show under the swimlanes after they have been moved out of the backlog and into the active sprint or kanban board. If they are not in the backlog then I suspect your board's filter is excluding the issues. Can you…

Hi @Andy and welcome to the Community! I'm not sure I'm following you here or not but... From the board if you click on an issue you will get the side-bar detail view and that layout can be configured. If you click on "e" while a card is selected then an edit screen dialog pops up (what you are showing). This is an edit…

re: @Steph Sjostrom comment... love it! reminds me of Christmas Vacation "The little lights are not twinkling."

While you can certainly delete a project (assuming you have delete permissions) but I would highly discourage doing so as you will never get it back. I prefer a more subtle approach by 'archiving' the project. Now in cloud there is no real archive function but you can accomplish by creating an permission scheme that…