Jack Brickey Expert

no way to do this OOTB. you might check addons, e.g. extension-for-jira-service-desk

ok. as Mohamed mentioned please go to project > project settings > screens and find the screen associated w/ the issue type (NCR) and edit it. click on the link to the screen scheme where you will find a list of fields displayed. Add Attachment and save it

duplicate post

I don't know any way to accomplish this certainly not OOTB. You might check this addon but I have zero experience w/ it so cannot say if it would help.

having customers in an Org allows the requestor to add other customers that are in the same Org. The email to the entire org when an issue is created is controlled by the "Organization added" notification. If disabled it will not go out, if enabled then everyone gets blasted.

@Jason Starr, not sure i follow. are you saying that you had the notification below disabled and were still seeing emails sent to all in the org when issue created? To be clear the issue captured in this thread has to do w/ the Organization added notification. I wonder if you might be experiencing a different issue? In…

@Lukas Gonzalez, what exactly do you mean? You can have notifications for updates but if already closed will they be updated? If you have a onetime event you could perform a bulk update w/ notifications set to send on update.

click the Administration button and see if you can add field - attachment. 

can you send a screenshot of where you are looking for this? the way you do this will depend on a number of things, e.g. cloud, server, jira-labs enabled, etc.

your image does not capture whether there is a "kanban backlog" area to the left. Does it exist? if so you would drag whatever statuses you want in the backlog to the far left.

there is no additional attachment custom field. Jira already allows for this of course. Depending on what your requirement is you might search the Marketplace if the current offering is insufficient.

Sorry I forgot to include the link - https://community.atlassian.com/t5/Jira-Service-Desk-questions/Is-there-an-issue-with-removing-customers-from-the-customer-part/qaq-p/793740

@Maria Taylor, what this means is that every column on a board must have a status form the workflow. Think of the boards and columns simply as filters for issues. In order for issues to appear in a column the column must have a status mapped to it. For example To Do column would have To Do status. If you are the project…

@Alex YAKIMOV, first just so it is clear, I do not work for Atlassian. I'm a user just like you so I couldn't say when or if the roadmap feature would be added to other templates. My guess is that they would not be offered on that template given the nature of how it works but that is simply a guess. With that said, you are…

yes. you simply leverage Calendars. You can define different calendars for different periods and SLAs. Please reference this article.

@Vipin Sroya, the buttons reflect the transitions of the workflow. so you must have that transition somewhere on the workflow. If you are still having issues maybe provide screenshots and reference where you are having issues.

BTW, I would not make them an admin unless you indeed want them to admin the project. If you are using JSW in conjunction with JSD, you can create a group called say "JSD Collaborators" and add your desired JSW users into that group. Then edit permissions to allow that group to have the desired permissions.

please check project > project settings > people and view his/her role(s) for the project. Then check project settings > permissions and see if the role has been provided the necessary permissions (browse, etc.)

"everyone" only includes users that have "Jira Software" application access it does not equate to public access. I'm not sure the best way to allow them to vote you could consider giving them Jira Software access but that comes at a financial cost and you would want to carefully manage permissions so that they cannot see…

Customers cannot access the Jira Application unless you add them as a Jira user which generally is not desirable. Customers under JSD only have access to Portal and email for JSD.

but if you are on Cloud then you should contact Atlassian Support since you cannot control the resources.

@Scot Mcphee, the reason I asked if your AOCD project falls under the NextGen category is that Epics are done differently (many things are different). The concept of Epic Links do not exist. Epics have children but unsure how to ferret that out via JQL at the moment. While I have not spent much time w/ Agility project I do…

You cannot. This question has been asked a number of times in the Community. If you look at the bottom right of this page you will see related content. In that list you will see Add customer without email and it provides more inf including link to open ticket to support. 

@Erika Sa, question for you on agility. Do the standard JQL epic functions work as before? I’m involved in this thread and wondering if it may be Agility related. Feel free to chime in there if you like. I plan to test it out tomorrow.

I’m curious, is this a nexgen Agility project?

@Jennie Sheridan, I would recommend you reach out to Atlassian Support for this issue. If you were on server I would say we should look at the logs but w/ Cloud you cannot to that. I would be interested if you see this continually and on other browsers.

that is correct. You need to create a new "Agility" project and you will then see it. You could consider creating an agility project and moving all issues to Agility but I would place a lot of consideration on this before proceeding. With Agility you get further simplification which may and likely will result in loss of…

thanks for jumping in Nic. Kelly, I was going back and re-reading the original question and am a bit confused on precisely what your goal is and what you did. Could you restate.

oh yes. you should not change the default scheme. create a new scheme for your project.

are you an admin? If so can you go to project > project settings > issue types > click Actions and add issue types to the scheme