Jack Brickey Expert

Nele, i believe the issue lies w/ your board filter. It appears you want to exclude all issuetypes except Stories for whatever reason. However, please include Epics. Try changing as follows: project = IG and issuetype in (Epic, Story)...

just add a new field of type selection or multi-select whichever is appropriate. You can't change an existing field but if not needed after adding the new one then delete it or remove from the project if other projects are using.

The only option OOTB is to use groups. It doesn’t hide the types but does obfuscate them. I would place the simple “Get IT Help” Request Type at the top and create an “advanced” group with the detailed request types. I believe there may be an addon that might help. Check the marketplace. 

@nirmala, if I understand your need try the following * create a filter like this - project in (a,b,c) and status != Done and severity = critical * Save the filte and make the filter public or shared as appropriate * create your dashboard and use the above filter for whatever gadgets you wish. JSD is based upon Jira core…

There are a number of addons that are worth exploring. While they may not give you precisely what you want they may give you what you need. Check the marketplace for ‘time in status’ or similar. 

The problem is likely that your workflow doesn’t allow editing of an issue in the Done status. You can verify this by trying to edit a single issue via the view issue screen. If that is the issue there are other threads on How to work around this. Just search for ‘edit closed issue’ or similar. 

keep us posted here. glad to assist for sure.

are you and admin? can you set up another SW project to see if you are getting same results. I'm a bit confused by the BETA label here to be honest. Are you on cloud or server instance?

@Catherine Sutliff, i'm guessing you mean the new Jira UI here. I'm unaware of any "beta". Assuming this is the case, I don't know of any loss of functionality off the top of my head and certainly not at the level of issue types. What type of project did the colleague set up. That might explain the default issue types…

yes. just get rid of the removed Status and simply add "removed" as a resolution value or just use an existing one e.g. "Won't do". IMO having the extra status of REMOVED is flawed but that is an opinion of course. :-)

well that is a different approach for sure. :-) But you should be able to achieve by simply creating a quick filter that equates to each individual project. So it looks like this: Board Filter: project in (a,b,c,d,e,f) quick filters: * project A: project = A * project B: project = B * etc now your actual JQLs will need to…

you can perform a Bulk Update after the field is added. You are limited (i think) to 1000 at a time thru that method. You could also do via an import (messy) but would stick w/ bulk update. see documentation for details

yes indeed that helps. Unfortunately I can't help you w/ this. :-( But expect someone in the Community can and hopefully will chime in.

@Hugh Guynn, I wanted to add to what Nic has provided here. There is one other option to consider and IMO, based upon all i have read above is the best option. Have "Removed" be a resolution and stick with DONE. The use case for why removed exists is well aligned w/ Resolution as it indicates why you are marking the issue…

I'm not 100% sure I understand your specific requirements but based upon how I'm reading it, you can use permissions. You will need to have some field/condition to limit the user's access.

and the lite version is free and may work for you.

@George Tasker the new UI should not have impacted the swimlanes but before concluding definitively let's look at what is going on. The quick filters certainly may have changed as they have been 'grouped' under a "Quick Filters" dropdown. So please check if the new view has that dropdown. For the swimlanes, can you go into…

sorry i could not be of more help. good luck!!

so i'm guessing you set the epic link for IG-4, 24 and 27 to a specific epic. Can you show me: * your board filter * an image of the epic itself (view screen)

status != closed and workratio > 100 regarding "deleted" is that a status? if so simply change the status bit to status not in (closed,deleted).

this is the way Epics as swimlanes will look... So make sure that epics are not excluded in your board filter somehow (Board Settings > General > Filter query). And make sure that the issues that are displaying are linked to an Epic.

@Nele Smeets, the epics as swimlanes should work. can you provide screen shot of your board filter as well as one for your board w/ Epics as swimlane enabled.

Niklas, thanks for attaching the RNs. @Irshad Peeran, as the originator of the question, we will leave to you to accept the answer.

I hope the translation is accurate. :-) если бы вы могли поделиться подробностями автоматизации, это помогло бы. основанный на том, что вы предоставили, я бы сказал, что делается попытка связать проблему с пользователем, не являющимся пользователем.

You need to upgrade. I believe the Backlog feature became available in 7.4 if memory serves. 

Well that is unfortunate on many fronts. That mindset is flawed for a number of reasons, e.g. you cant easily track the number of bugs against a feature/dev item. But let’s not turn this into a religious war. :-) ultimately if the business isn’t going to embrace Agile then you should simply use Kanban and agile-like…

@Umar, the jql looks functionally accurate. Does it provide expected results? It does appear pretty lengthy and likely can be simplified around the statuses. As well you definitely don’t want to use dedicated dates as that becomes a pain going forward. Try using beginning of week and end of week or similar. Which statuses…

My advise, based upon experience, is to decouple testing from the dev. Let Dev use scrum and testing be independent. When dev is done then test can open bugs against the ‘feature’. This would be done by opening an issue and linking it to the done issue. You can even consider having a separate Kanban board for the…

BTW, if you think you might want the request type later you could simply hide the request type from the portal. When you delete any existing issues of that type will remain in the system so you can find and customer can still see/act on them.

@Beth Starr, sorry for delay in getting back to you. I lost this in my notifications. Any recent findings during my absence?