Jack Brickey Expert

It is still an option in my instance. . I assume you are on Cloud? If so are you looking at the new issue view or the old view. If the new view be sure that the Issue Layout includes the Labels field. I find mine under the "Show more" link.

@Nir Malchy , welcome to the Community. First understand that a Queue is little more than a query of the database. If a user has browse permissions (as any agent would) then they will be able to see all issues. So even if you could hide the queue another agent could go into the search for issues function and run a query…

so then the things to confirm: * the issue is indeed associated with GIEO project (expect it is) * check the channel the issue came in on. it needs to be via the portal not email or the Application itself.

i would reach out to the admin. I'm betting there has been a recent update.

i expect that one or more of the SLA conditions are not being met. To assist you further I would need a screenshot of your SLA page and the detailed view of one of the issues not displaying the SLA. Alternatively look closely at the details and figure out why the issue is not meeting the SLA criteria.

 I found this this article. I wonder if it might explain your issue?

Hi Phil, nice last name! almost as good as mine. ;-) So this is sure odd. I'm on cloud and certainly not seeing this. To the best of my understanding there is no configuration for this so either it is a browser interop issue (try another browser to test) or it is a bug introduced or both. Have you recently upgraded?

no. while you can include on the individual cards you cannot change the summary behavior. 

You might want to look at this article about issue collectors 

Can you share screenshots that shows where you select "PROD..."? When entering the query have you tried advanced mode and entered the following? sprint = "PROD if you do that do you get auto-complete w/ the option you seek?

are you on server or cloud? can you share a few screenshots that exhibit the issue? What I would want to see is an image that shows an issue w/ all three components listed followed by a query and the results that should pick up the issue but does not.

@Nitin_Deshpande , first note that i closed the duplicate question posted to focus on this one given there was already discussion. You mention that you don't have administrator permissions on your "laptop". Jira permissions are w/in the application not the device. If you are a Jira system admin then you should have access…

correct. links are really just references between tickets. Jira does not perform sum-up functions between linked issues. For this to work the issue needs to be a child (sub-task) of the parent.

let's clarify what your requirement is... * if you wish to return only issues that have all three components: ABC, EFG, IJK then you would use - component = ABC AND component = EFG AND component = IJK * if you wish to return issues that have any one of the components then you would use - component in (ABC, EFG, IJK) you…

ok so i just reread this and wanted to reiterate my earlier response. If you are using inbound email handler to create a ticket for reporter that is NOT a user then Jira cannot respond to them because they are not in the system. Example... Assumptions: * Jack is a user defined in JSW instance * Bill is not a user defined…

@Carlota Vendrell , is this issue still open? If not please post your resolution if possible to benefit others. If you are still having issues LMK.

cleaning up old questions that have fallen thru my radar... this isn't possible. the customer can see who is participating only via the portal view.

@Fayaz Abdul , is this still an issue for you? If not please post your resolution here for others to benefit. If the issue continues I can reengage w/ you.

cleaning up old questions that have fallen thru my radar... Queues are per project and Agents are per project so the Agent must navigate to the specific project to see their queues. That said, if you have JSW as well then the agent could create their own Kanban board that combines all their various projects into a single…

@Scott Harman , is this still an issue? If not please update here w/ the resolution if possible.

@Neeta Dubey , i'm trying to circle back on old issues that have fallen thru the cracks. Has this been resolved? The last screenshot seems to convey the user can't login?

There currently isn't a means of exposing "linking" issues via the portal. This must be done from within the application by the Agent. The customer could reference the existing issue when creating the new issue which could then be used by the Agent to link them. If desirable the Agent could add the issue key in the…

there is no way to do what you are saying as far as color. You can change the description of the field to include "recommended".

yep the "in" operator reflects an "OR" scenario. you have to be explicit w/ "AND"

Hi Evgeniya and welcome to the Community. The request is a bit ambiguous but I would offer the following solution to see if it meets your needs. Create a filter and add a subscription that reports daily. example filter... project = myproject and originalestimate is empty and createdDate > startofday you can play w/ the…

If you are trying to identify the group that is originating the issue, e.g. DEV, QA, CUST then you could create groups, a custom single-select field and use an addon to assess if the creator is in membersof (""). if this is what you are aiming for and need further assistance to make it happen JLMK.

This is not possible to do OOTB. You can check the Marketplace for an addon. 

They are considered breached once the timer has reached zero. What are you looking at that conflicts with that? If you create a filter for breaches issues they should show in the results. 

you could add a custom field to place the email in. Either a simple text field or a URL field a/ the mailto:first.last@company.com format.

i'm guessing you have a starter license that limits the number of users. In order to stay w/in the constraints of a starter license you will need to deactivate (and should) unused users.