Jack Brickey Expert

There are a couple ways to do this. * 2-boards: don't include the Spike items in the 'release' board. manage them independently on another "Spike only" board. and never 'release' on that board. To do this, add "AND issuetype != Spike" to your current boards filter then create a new board "Spike only" to be only Spike…

you might want to look at the Marketplace addons. The builtin satisfaction surveys in JSD are quite limited IMO. I don't know if any provide a post-issue survey solution for you though.

Are you saying that the team is changing the Original estimate or the Remaining estimate? IMO, they should leave OE alone and only update the RE even if the determine that their OE was flawed. That aside, regarding what is displayed, do you want to see how much effort remains on the cards? If so edit the board’s card…

Thomas, below is an article that deals with migrating from server to cloud that, while likely beneficial it isn’t exactly what you need. If you are just moving some projects what I recommend is the following: * backup your current server (always a good idea) * stand up you cloud instance * build your projects, workflows,…

Which of the following best conveys what you are trying to do? * add issues from project B to an existing Kanban that currently displays Issues from project A. * create a new Kanban board that has project A and project B issues. * or something else. in #1 you would edit the filter of the existing Kanban board via Board…

For this you are going to need to go beyond the capabilities of JQL. You could use and addon like Scriptrunner which will allow you to compare dates or you could export to CSV and use Excel. Basically you need something like Resolved date <= sprint end date AND created date >= sprint start date what might be of interest in…

Yes to both

And if you do not see “reports” in sidebar go to project settings > features and enable reports.

In NG you get two reports: Burnup and velocity. The Burnup allows you to view by sprint and estimation method. In that report you see the performance to plan and a list of all issues in the sprint. Otherwise you can run a JQL search using the sprint name.

It sounds like what you are trying to do is to expose the transition on the portal only after some time has passed? Such as you don’t allow the customer to immediately escalate an issue but if a ‘day’ has passed then they can. If this is the case I don’t know of any means of making this happen. I don’t know how you could…

i recommend a custom field for Tiering. Everything comes in at T1 and if it needs to be escalated then it is changed to T2/3. From there, you can use Queues, Automation, Groups/Roles etc. to notify folks as needed. You can easily illustrate the different tiers on Dashboards. 

NG projects do not allow/require customization on notifications. 

 Assuming I understand your request correctly, you should not do this through a first response. Rather you should do this in the form itself at creation add the necessary custom fields and require the user to fill them in. 

yes. don't delete stuff...bad idea. Simply move to Done and use the Resolution to indicate "won't do", "unnecessary" or whatever resolution value makes sense to you. Talk to your admin about adding a resolution code to meet these needs.

the way JSW/JSD work in this regard is to allow you to define schemes (templates). Then when you create a new project you simply share the scheme w/ this new project. In fact when you create a new project it gives you an option to share the configuration of an existing project. TBH I cannot recall what all gets shared but…

it will change as it is specific to the project. Issuekey is proj-# so it will change.

Q1: you can use automation to set the request type if the issue comes in thru the app I think Q2: again, I would check the Automation capabilities.

so a lot of things to consider on email notifications and it is really challenging to troubleshoot w/o seeing it first hand. Here are some things to consider/try/inspect: * agents cannot be customer. make sure to check project > Customer and look to ensure the agent is not listed there or and organization if you are using…

ran across this old issue. i think the cause was that i had an agent also listed as a customer.

not sure what you mean by "Type values". Can you explain?

I would definitely try that with one agent. I’m betting that is it. 

Unlikely but this has bitten me before - make sure the agent is not also listed as Customer. 

correct.

go to the project > reports page and view sprint report. select the sprint of interest. you can also create a JQL if you know the sprint number.

yes but I didn't consider "<account>" to be public. for example i have a NG test project in my companies instance but that doesn't mean you can access. it means any user currently defined in my Jira instance can access. 

i answered the removed duplicate post with the following... if you have a custom field in Proj A and you move the issue to Proj B that does not make use of that same custom field, yes it obviously will be gone. Options, add the custom fields from A that you are interested in keeping to B before moving or add it to a…

glad u got it resolved!

have you looked at the Sprint burndown or maybe better the burnup reports? I would start there and see what you feel is missing.

your projects are open to the public by default? When I create an "anyone" project it is restricted to anyone w/ access to my companies domain. Disclaimer - i don't use NG for anyone projects but some of my users do. You might want to give feedback to Atlassian via the Feedback link.

Hi @L Lattier , no this is not possible unfortunately.