Jack Brickey Expert

@Matt Doar, this is very sad my friend and note that is a nightmare not dream. LOL

well you can create a filter and export to CSV and open in excel. Not sure if that is what you are looking for.

yes. i use and here is a solution to try...

hmmm, what fields are marked as required. for email only summary and description can be required. But I didn't even think it was possible to make other fields required. has been awhile since I have set up a new JSD project though.

ok so surely a bug associated w/ Gmail interop. I just added my gmail test user to the subscription I have and what is weird is I don't even get the "Customer Request Type" column but in Outlook it is there clear as day. @Matúš Klaudíny, I recommend contacting Atlassian support and please reference this thread and place…

this is a good one for sure! Yay for Susan and I as we have a bone w/ some meat on it. boo for you as you are suffering thru it. :-) This is sure smelling like a bug. I'm continuing to contemplate possibilities. In the interim you might want to open a ticket w/ Atlassian Support.

@Matúš Klaudíny, like Susan mine are showing fine and i'm on Cloud. So we need to understand what is different for you. So for sure you have checked INN-618 and 617 and you see the request type in the detail view? Can you try to remove the CRT from the filter, rerun to show it is gone and then re-add, just for grins?

Did you verify that the issue actually has a request type in the detail view?

Eric, as this is a public forum I would recommend against sharing your url. You might want to edite that out though in reality others w/o accounts will not be able to access. As I do not work for Atlassian I cannot access your instance nor would you want me to. :-) With all that said, you cannot change the format/columns…

It depends... If you are on Cloud... * Classic project - You can copy the board and take ownership of the new one and delete the old one * Next-gen - there is not ownership. i "think" everyone that has access has full access if you are on Server it should be the same as the "Classic" answer above but not 100% sure.

Ok so the image is a sub-page not the main help center page I’m guessing. I’m really unsure of the cause. I can take a closer look at mine to see if I observe this but even if I do I’m not sure I can offer a reason/solution. You might reach out to Atlassian Support.

I’m aware of it only because I have seen others speak of it in the Community. Doesn’t hurt to trial it.

Please see this document /set-up-a-knowledge-base

Then you simply need to remove the FixVersion on those issues. You could use automation (addon) to blank the field if issue resolved with any of those resolutions.

please see this article - setting-up-service-desk-users which conveys Remove customers from a project * Go to Project settings > Users and roles. * Hover over the user or group you would like to remove, and then select the trash can. If the customers have Jira accounts or created their own accounts, then a Jira…

The answer remains the same. I don’t expect this to change TBH but you never know.

The new view appears when working with Kanban boards. Do you have a Kanban board set up for JSD project? If you are working in queues and click on an issue you get the detailed issue view not the new view.

I’m not seeing this on my instance. I wonder if you could try enabling the new portal look and feel and observe results. If you are the admin, on the portal click Customize and then toggle the new view on. You can easily revert by toggling back off.

@[deleted], I’m unclear what the “released-report-all-issues” is exactly. When I go to Releases I show unreleased versions by default. Here I can select to include unreleased as well. If I click on the version it takes me to a page with numbers (warnings, issues in versions done, etc). From there, if released, I can…

Can you share a screenshot of a Jira view you are trying to mimic in JSD? below is a JSD project. This is seen when using Kanban boards which isn’t all that common with JSD but doable.

Correct on all accounts. Glad you got it working! Another “trick” on Closed issues is to create a transition from Done to Done and give the transition a unique name like “redone” and set the post function. Then use bulk edit to transition all done where the resolution is empty.

Yes

It isn’t a function of your board. The board is a ‘slave’ to the workflow. If you are the admin then find the workflow(s) associated with the project(s) that are not behaving as you would like then do the following for each: * edit the workflow in diagram mode * double-click on each and every transition into “Done” or…

Try changing your board filter to exclude “won’t do” when you then click “release” those will not be included. add to filter something like ... AND Resolution not in (“won’t do”, cannot reproduce”)...

@Devin Martinolich, setting the resolution is certainly important and TBH I wish that, OOTB, it was setup that way by default. That aside, you simply need to setup you workflow and screens to accommodate/require this. On any workflow you should do one of two things, either: a) use post function to set the Resolution to…

@Isaias Salazar Torrealba, welcome to the Community. You will need an addon app, e.g. Scriptrunner or Power Scripts, etc for this. While I don't use either I know they support this. for example Scriptrunner has a script function called "haslinks". Cheers!

from what i have seen NG is intended to appeal to a no-admin-needed-environment. the more customization you allow the more you will need someone to admin it. I still stick w/ Classic as it meets my needs better at this point.

@Amy_Washburn, it appears to me that they have reformatted the roadmap so unclear where it falls at this point TBH.

glad to help. just an fyi... Atlassian employees will be designated by an "Atlassian Team" lozenge by their name here in the Community.

I couldn't say TBH as I'm just a user. There was an AMA several weeks back. You could post a question to Jason Wong (PM) there to see if he has an answer for you. Regarding the data on the roadmap link I provided, I suspect fix version will be incorporated under either of Build Integration or Deployment Integration but…