Jack Brickey Expert

if the stories were in the right-most column of your scrum board (done) at the time you actually closed the sprint they should not be in the backlog. * Can you share a screenshot of your backlog and the culprit stories? * Is this a new issue? Was it working before? * If it doesn't mess you up then, as a test/recovery, you…

came across this old post so expect you already solved this but just in case... Closing a sprint only removes those items in the far right column. Since you moved (seemingly) the "Closed won't do" from the right column to the left then they will not be considered complete when closing the sprint resulting in them showing…

Are the stories marked as Done status? Are there any sub-tasks in the stories not yet complete? You need to either move the stories to Done manually or configure it so that they automatically move to Done when all sub-tasks are complete.

Got it! I have done something similar though in the end I never really was thrilled w/ what i created. It felt to heavy and un-agile for sure. Ultimately, I think a single Kanban would have worked out better. Regardless it went something like this: Dev - To Do, In Progress, Ready for QA with the last status being in the…

@Jasmin Palanca, welcome to the Community. Are you asking how the customer can do this from the portal? If so, you need to have admin rights and you need to update the associated workflow to expose the transition (resolve) on the portal. You will find a number of other threads that explain this in detail including example…

Hi Simon, It does not happen to my cloud instance using Safari. I would definitely recommend reaching out to Atlassian Support

@Matthew D'Angelo, as Nic mentions videos age out quickly. With that said a search in youtube on "jira cloud tutorial 2018" turns up at least one. I didn't watch completely at all and my rating of what i did see would not be great but it is something.

@Shadi Sultan, if you look just to the right under "Releated content" you will find what you are looking for. Also, you can simply search in the community to find many threads on this discussion. 

@Alicja Snarska, agree completely. As a long time manager I believe in empowering folks to manage their time. Using SLAs will allow you to easily monitor time-managment issues and then work w/ the team to correct.

FWIW, i experience a blank page on Jira using IE long ago. It had to do with IE compatibility mode. Here is the thread discussing this. Likely unrelated but for sure I would try another browser to rule it out.

@Abhishek Gaur, just curious here; what is your end goal of having two different boards?

@Michael Strickler, after reading your inquiry a couple times I believe the key thing you are looking for is the "age" of an issue and being able to display that in a filtered list. Going off that assumption, unfortunately Jira does not have a calculated field for this. Please feel free to vote/watch - JRASERVER-12958.…

How about this. Change the workflow to have a Condition that requires Assignee before the issue can be transitioned from initial 'new' state to the next state. Limit who can set the assignee and thereby prevent transitions.

you cannot do that. any issue that is a child of a parent is by its very nature a 'sub-task'. You could create a new issue type and maybe call it something like Task1 and make it a sub-task type but it is still a sub-task. Why do you want the child to be a "Task" specifically? What properties does the "Task" issue have…

@Ricardo Gonzalez, i'm a bit confused. You don't create a task of a task. If you want a task you create a new issue and if you want to you can link to the other task. The purpose of the Create sub-task is that it creates an issue under the current issue so you have a parent-child relationship. I suspect you realize this…

Aha..."that" category is simply a customer label you can change that all day long w/o impact.

I would recommend you reach out to Atlassian Support

Hmmm, i have never moved a JSD project to say Software before. For sure they are different beasts and while it should work I would not be surprised if some weirdness develops. I would expect that modifying the workflows once or prior to moving would be wise.

if you want to say fire an event or send an email each and every time someone transitions a lower priority issue to In Progress when there are open higher priority I would suggest looking at a scripting solution (Scriptrunner, Power Scripts). I don't use either currently so can't really assist w/ the syntax.

@Alex Nguyen, yes can you please open a new question. This scenario is quite unique and is not an answer to the original question. I attempted to move it but "move" feature is having issues at the moment. :-( Once moved we can delete this question here.

It sounds like you are looking for a queue manager that prioritizes agent’s work by handing out issues, controlling what they work on first. Personally I would view this as an employee training issue. That personal perspective aside let me answer your question. :-) I don’t know of any way to hide issues of lower priority…

You need to create an incoming email channel. Please see this document for the details. Note: the link is to cloud version however you can easily navigate to a server version in the top right hand corner of the doc.

@Simon Carlstedt, this seems odd for sure. If you repeatedly refresh the page are the results the same? How about other browsers. This seems like a bug and depending on the answers to my questions would suggest reaching out to Atlassian Support. When I have a moment I will test my instance for the same.

Can you try to create a board outside of the project. When you create the board use the business project. It should ask you for a location and here choose your profile. If you are successful you should be able to add the board to the project as a link. At least this is how cloud has worked for sometime and wonder if it is…

I'm not familiar w/ Aha. have you looked into creating a dashboard and leveraging gadgets and filters by version?

@Angel Casas, i'm not quite sure what you are asking here. Focusing on terminology here in hopes it will make things clear for me... Groups = how you group the customer Request Types, e.g. "Common Requests", "Logins and Accounts, "Computers"... Request Types = the types under the groups, e.g. "Petitions", "Get IT help",…

@Julia Dudni, welcome to the Community. As a point of education, the Community is made up primarily by users like yourself so we have no way to change the software. While there are certainly Atlassian team members that support the Community the forum isn't meant as input into improving the product. For that you should…

Have you considered using a Jira scrum board? In the backlog board you will be presented with two collapsable sidebars: Epic and Versions. You can expand Versions and simply drag issue directly into any defined unreleased version. see example below.

I haven't been bugged by this in some time. However, i recall it used to happen to me and I want to believe there was an option presented to 'stop notifying me' but I can't test that. By in large I have elected to use the backlog as IMO it is the only reasonable way to manage a big backlog and set priorities of what to…

@Ricardo Gonzalez, there are lots of ways to group tickets. The best (?) solution depends on your end goal. Basically all rely on simply creating a JQL filter. Here are some ideas: * If your agents are going to use this grouping actively and frequently then I suggest creating a Queue in your project and define the…