Jack Brickey Expert

yes likely the reason.

there are two 'project names' in JSD - one that is for the application and one that is for the portal. you change the application project name here - project settings > details > Name you change the portal name here - project settings > portal settings > Name

Hi Dina and welcome to the Community! I feel your pain and in fact accuracy is very dependent upon adhering to the sprint rule - 'thou shall not allow sprint creep'. My best advice and options are: * get the company to fully support locking down sprints. If something comes in after a sprint starts it can be placed at the…

Hi Daniel, I have used an addon call Epic Sumup once upon a time and it worked pretty well. Here is a link to a list of possible addons. I don't know of a way to do this natively. I would point you to a good read on another thread that is shown to the right under Related content - Summarizing story points from sub-tasks in…

@Kseniya Perapechyna , you may want to reach out to Atlassian Support. Most of us are non-Atlassian users just like yourself. If you have found a bug then report to Atlassian.

those are not JSD projects. they are Jira projects. The widget is for JSD projects only.

you need to prevent deletion. deleting issues has all sorts of bad side effects. Deletion should be restricted to system admins. To your specific request, you cannot prevent based upon "has links".

maybe....are you expecting the status to change from Done once it is released? That doesn't happen. Released is associated w/ a Fix Version and it is binary: unreleased or released. If you want, you could add a status "Released" and manually or thru automation transition the issues to "Released". Keep in mind that the…

are you on Cloud? In cloud if you are an admin then in the project go to project settings and in the left side bar you should find "Widget" about half-way down. If you are on Server I don't think it is available but could be wrong.

i'm not familiar w/ "deployed". I don't have that in Cloud, are you on server? I'm wondering if this is a server feature or if it is a custom status or something in your instance?

i would guess so based upon the noted fix version of 3.13.1. I recommend upgrading.

you could use a dashboard and add a pie chart to display by issuetype.

that is because your questions are not specific enough. but let me try to answer... "you click on the assignee field and type in their name"

duplicate

@koteswararao , this is a duplicate of this other post. I'm confused as to what you are asking. If someone is assigned and issue then they simply log in to see what issues are assigned to them and work them to closure. This is basic Jira operation so you need to review the documentation to understand how Jira works or go…

it is for agents.

FWIW, i would not accept this as an answer. If you get something back from Support and/or find the cause, please post as an answer and accept that. In this way future searches might be helped.

you aren't by chance using gmail are you? note that archived in gmail are still there. But given you said it is truly new i expect this isn't it. Please contact Atlassian Support.

ha! well that is new. I see it as well in my instance. gotta love cloud. its like Christmas every day. ;-)

Assume you have reviewed the documentation already? If it doesn't help you might want to check the Marketplace for an addon to help w/ this. 

correct. i need to be paying attention to the collections more closely. i was reading the question and not looking at the fact you posted in JSD. :-( Alexey is correct.

are you on cloud? NG is only on Cloud. If so, verify that if you attempt to create a new project you see this... If you do not see then it could be that your admin has disabled NG.

what version are you on? I found this bug fixed in 3.13.1 - JSDSERVER-5778

i must apologize! I did not notice this was even in the Jira collection. I simply assumed, given the question, that you were asking about JSD. :-( Indeed if you want approvals in JSW then you need to go the addon route. sorry!!!

are you using a brand new email address for the new project? If the emails has emails in it then it will fail as the error indicates. JSD checks for this to protect against associating an email that might have thousands of emails which would result in 1000s of issues being created. Try logging into the email and checking…

sorry this makes no sense.

we need more info. The questions, if that is what they are, seem very basic. I would start here - Jira Software Cloud Documentation

you will need to provide more info. What fields are not exporting?

you should add a "Clear field value" post function to the transition back to clear the Approval field.

Tal, i'm confused. I thought you already were successful in setting up approvals in the workflow? The link you provided earlier should instruct you in how to create workflows w/ approvals.