Jack Brickey Expert

A screenshot of your SLA will definitely help. Note, there is a current bug outstanding (JSDCLOUD-5686) associated with SLAs not stopping but before we jump to conclusions let’s have a look into the details of your specific issue. 

BTW....I really think you should consider two different projects. it would make things much cleaner. Mixing Support issues with Sales issues is unconventional. Again...just an opinion.

ah yes I recall that discussion. To be honest I think that method might lead to more issues down the road but that isn't based on anything more than a feeling so fell free to toss that comment aside. :-) you can most certainly change the issue type based upon various conditions. it may require a plugin though. Unsure if…

I'm still not quite sure I understand. Do you have a single project or two projects (support, selling)? If not why not is sure seems that they should be different projects. If a single project how do you have two emails feeding it? Maybe this is server and server allows that but didn't think so.

добавьте себя в качестве агента службы поддержки и выясните, разрешает ли он вашу проблему. hopefully Google Translate worked and I didn't just say something horrible. :-)

@Guillermo Rosas, we are going to need more info here. Please explain the use case. Under what conditions do you want to change the issue type. For example... I want to automatically change the issue type from Bug to Improvement when Component is New Feature.

there are a number of existing threads in the Community on this already. Here is one

Speaking from a position of someone that approves purchases for the company here is my advice: * What problem(s) are you solving and can it(they) not be solved in today's environment?* collaboration * reporting * tracking * usability * flexibility * supportability * integration w/ existing tools * etc. * How will…

your original post did not convey that you are setting up swim lanes by stories. Indeed if that is your intent then that is all you need to do to get story swim lanes. Can you provide an image of what you see? Stupid question but, do you have stories created? 

@Chris Miller, on the surface it appears your license has expired. You can verify this by going to settings > billing. If that is the case you need to renew. If however your license period has not expired then contact Atlassian Support.

My only suggestion is to switch back to old, reorder and switch back. :-( that and open a suggestion for Atlassian to add this into new UI. Note, @Matt Doar suggestion should work but need to get the right url whcich you should be able to discern via old UI. 

If the clients can browse the issues of a project then they can view the time logging. Time logging cannot be uniquely treated. The only thing I can offer is to maintain separate projects, those that can be browsed by the clients and those that cannot. 

@[deleted], I regularly switch back and forth but have not seen this issue. As you have described it I would consider this a bug and suggest contacting Support directly. it would interesting to try a different browser once you switch back and see what happens. 

Unsure what you mean when you say unable to scroll... can you provide more details? Are you able to switch back and forth between UI experiences? When you do can you refresh the browser and/or clear your cache?

@Ronen Erlich, I'm not 100% sure what you mean by the "main SD page" but let me add some info here that might help. First, are you on Server or Cloud variant of JSD? The reason I ask is that I am on cloud so what I see may be different than what you will see if on Server. BTW, it is always a good idea to add a label/tag on…

there are a number of ways to achieve this. The first I would consider is to use Components. The Components would represent the teams w/in the department. If your customers are aware of the teams then you can make Components a require field and even if they are not aware if the naming of the Components is clear then they…

let's bring the junk piece out outside along w/ created date and see what happens. (assignee in membersOf(mimo-full-team) OR (status changed to (Resolved, Closed) by membersOf(mimo-full-team) AND resolution != Duplicate))) AND createdDate >= "2016/01/01" AND labels not in (junk)

good question...I haven't done this in a long time. then need hasn't been there for me. It would appear that the new UI has lost this capability as far as I can see.

that should be happening already. are you saying it is not?

no

@[deleted] Great! If you would, please accept Susan’s answer

Did you install JSD as an application in your Jira instance. System admin > applications.

Yes that would be a reasonable approach. You may wish to use components to continue to distinguish the 2 (or 3) ‘sub-projects’. In that case set the component on all issues in the biggest project first before moving the 2nd project in. Finish with custom fields, screens, etc. good luck!

just guessing here but maybe @Anna Marcilla has updated a shared workflow but not a system workflow. If a shared workflow has been undesirably updated then simply edit and change back to original. If you made a copy of original when publishing the new version restore the backup.

Excellent! I can see where the 'holographic me' will be able to answer Community question soon allowing me lots of extra free time! WooT!

well that is strange. It looks like you are on server. On cloud it works fine for me (see below). Hopefully someone on server can add some color to the problem you are experiencing.

@Jessie, wait for the sprints to complete and, before starting another sprint, delete the unwanted board. As long as there is an active sprint you can't delete.

@Rodolfo Möller, I'm sorry my answer was not what you had hoped for but the initial question was generic as well. Please understand that I'm just a user like yourself not an Atlassian engineer or product manager. Fundamentally the decision, IMO, comes down to whether you want/need to develop software or not. If so then…

where are you trying to add groups specifically? 

core boards are good for basic project management workflows. not so great for SW projects where you need time tracking, scrum, burndown report, etc. For the later you would want agile boards.