Jack Brickey Expert

Ok so the observed behavior is certainly due to the boards configurations. If you move an issue from Closed back to the development board it will be see as sprint churn and increment the count. There are a couple of thoughts I will share here FWIW but keep in mind they are only my opinion based upon my experience w/ agile…

ah...so i'm guessing that 'Closed' status is not your right most column. Can you provide a screen shot of your board settings > columns. It would also be useful to have one of your workflow as well. Recall that the right most column is the status that represent the issue is done (resolution set to done) and the burndown is…

Try something like this. of course replace my name. :-) You can leave off the first part if you want to include the ones the person is currently assigned. assignee != jack.brickey and assignee was jack.brickey

fair question. I would have to run some tests to see the behavior firsthand but my tests might not reflect your observations. However, keep in mind that the count in the chart is based on the Resolution field. You need to see what happens when an issue is reopened. The proper behavior is to have the Resolution field…

You could use automation (addon like Automation for Jira) and check the Summary field. I'm not a big fan of automating on free text but since all you are doing is setting an Assignee and then if wrongly assigned the person could reassign then harm is low except for delays. I would certainly recommend using a field…

yes it is pretty straightforward at least for what you are trying to do. I would go to the Marketplace and review the various automation addons. It might be that Automation for Jira would also meet your needs and there is a free version (Lite) available. You can always trial the addon before buying.

Thanks Jason and no worries we all had to start at the beginning. You will learn quickly. :-) So fully understand what you have conveyed. However, my question still is unanswered so let me rephrase. Who get's assigned an issue? How do you determine the owner of an issue? The reason this is important is that if you wish to…

If you are getting that message then you are not a system admin. Please go to project > Project Settings > Permissions and look at "Delete Issues" to see if you are in any of the associated groups that have permissions.

@Jennifer Purdue, welcome to the Community. The behavior is not normal OOTB behavior. You must have some automation or other rules configured to do this. For sure that would not typically be desired behavior. Are there other Admins that might be able to configure the system? If so I would suggest checking w/ them.

@John Halbert, welcome to the Community. I would start by looking at the full History of one or more of the issues to better understand the transitions. Unless Reopened is actually a status you have created it may just be telling you it was previously reopened, e.g. To Do > In Progress > Done > To Do (reopened) > Done

@William Yamashita, welcome to the Community. You can't do this OOTB, you would need an addon like Scriptrunner or Power Scripts. However, I would encourage you to think carefully about the solution as I suspect others would not want to have that same behavior and suddenly see their issues being inexplicably closed. All…

это дубликат запроса. посмотрите эту тему. - https://community.atlassian.com/t5/Jira-Service-Desk-questions/Customets-for-support/qaq-p/874365?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_question&utm_content=topic

это дубликат запроса. посмотрите эту тему. - https://community.atlassian.com/t5/Jira-Service-Desk-questions/Customets-for-support/qaq-p/874365?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_question&utm_content=topic

You restrict access of customers to projects by ensuring they are not listed as a customer in the project. Keep in mind that if you have a customer in an organization and you have that organization listed under the Customers for the project they will have access. I'm not sure I understand your second question. However, to…

@Ian Wright, welcome to the Community. I would start by looking at your Customer Notifications. Project > Project Settings > Customer notifications. 

@Natalie Homer, sorry I don't understand how this has anything to do w/ Jira. What am i missing?

@Jason Knight, to provide you w/ the best response it would help to understand more about your requirement. Are you wanting to assign all sub-tasks to a single individual or do you want to do this on a conditional basis. If the latter what are the conditions? BTW, I'm not sure what you mean by "having the service desk…

@Claire Liu You are most welcome. If your question is now resolved be sure to click the checkmark above to accept solution as it helps others when they have a similar question. If you still need help on this JLMK.

so my filters were something like this * Board A - project = ProjectA * Board B - project = ProjectB OR (project = ProjectA and assignee = shared-resource)

Adding to what others have said here. Regarding #2 you can do this natively using JSD Automation.

There is no way to include the linked issue status on the card. I had a similar situation at one point and will share here in case it helps. * project A and project B work in independent scrums and boards * project A needed support from one resource in project B * Team A would create issues in project A for resource in…

@Frankie Henderson, Welcome to the Community. Boards are simply graphical views of issues in one or more project. What displays on the board is governed by the board's filter. Have a look at the filters for each board (Board settings > General). I suspect you will find an overlap in the filters that results in the issue…

@Diogo, I am not sure what you mean about service desk automatic updates. Are you on cloud or server? Can you elaborate on you issue?

@Roberto Ialino, I would recommend first reading this article. The link is for cloud but you can certainly switch to the server version via that link (top RH corner). Basically, you need to: * assign a Request type to your email used for submitting request * as Jason indicated for the chosen request type you need to have…

Assume you are asking about server. According to the versions shown in documentation: JSW - 7.11 Bitbucket - 5.13 Confluence - 6.11 Bamboo - 6.6

I suspect they are canned and un-editable values TBH. Would you mind sharing a screenshot of the new functionality so I can familiarize myself with it. I would like to search the doc for this as well so if you could share your version that would be helpful.

@alexsheppard11, welcome to the community. I am on cloud and have not seen this option so likely a server feature. Regardless, you could choose to simply edit the board filter to not include Done issues older than x-days. Or if it is a temporary hide you could create a quick filter.

Are you on server or cloud? In my cloud instance I have the ellipses with the following options: delete sprint, reopen and view in issue navigator. What I see in your screenshot is that those options exist on the screen. So I wonder if your version has done away with the ellipses. What is it you are trying to accomplish…

@Claire Liu, welcome to the Community. Things may have changed as Agility is still under beta AFAIK so take the following w/ a grain of salt. Done issues will age off the Agility board after 2 weeks. The issues, of course still exist they simply are filtered off the board. You should use the Search issues screen and JQL to…

Ha! Larry's answers are precisely mine as well. When I introduced JSD replacing Spiceworks it greatly improved the way the IT group works and the visibility of those efforts. Before it was very difficult to monitor incoming tickets and closure. Now, with dashboards and queues we have improved controls and…