Jack Brickey Expert

Have you tried command+

Maybe I am not understanding but you can easily link a bug issue to a story issue. If you wanted to require that linking, I.e. every new bug should be linked to a story then you can have a unique workflow for the bug and use the Validate function on the create transition. 

Hi @Prashant Neharkar , by default Severity field does not exist. You can certainly add it as a dropdown list single-select.

There should be an ‘only my issues’ or ‘assigned to me’ QF by default. If not simply add one. This allows the current logged in user to filter out all it those assigned to them. ”assigned to me” - Assignee = currentuser()

Does your vaild use case involve a parent being closed while sub-tasks remain? If not, I might approach the issue differently, such as use automation to close any sub-tasks if parent is closed. Normally, I see scenarios where, when the last sub-task is closed the parent is automatically closed but you could implement the…

You can simply exclude the component that you’re not interested in your Jira query filter. example - ...AND components not in (2, 3, 4)

you can either consider exporting all issues via a filter search and include the story points then use excel to process or consider an addon like Epic Sum Up

Try the following...does that give you what you need? assignee = jack.brickey or assignee was jack.brickey

There isn't a way to accomplish this OOTB. Maybe there is an addon that supports this but I have never looked for one.

@koteswararao , I would recommend going thru this documentation on getting started - get-started-with-jira-service-desk

introducing Moonpie. He is just one of the dogs.

those Sphynx cats give me nightmares! looks like he is reaching into my soul. :-D

I’m not familiar with site24*7 But if that tool can generate an email when an alert is created then it could be sent to Jira service desk which would create a ticket. 

Please see this article permissions-overview

@koteswararao , I’m unsure how to respond to your inquiry. It sounds more like a statement of what JSD does already. * It has a portal (landing page) * it has forms and when completed it results in a new issue in JSD * it has queues * It has required fields * you have the ability to create a project the only thing that…

That article is for Server. The archive function isn’t available in cloud. What I do is to create a Project category called Archived which acts as a label the I create a permission scheme called Archived. This scheme restricts all access to admins only.

You need to ensure that the sub-task issuetype is associated with the JSD project. Verify the following... Project - project settings - issue types - action - edit issue types - add sub-task

is it possible that you are using NG project here? If so epic link doesn't exist for next-gen.

"Status was resolved by" doesn't exist as you found. Can you not assume that "status was resolved by" is equivalent to Assignee AND status = Done? In other words would using the following JQL filter work? project = "IT project" and status = Done and resolutiondate <= now() and resolutiondate >= 2000-01-01 then apply that…

green should certainly be those issues resolved. you indicate "...have resolution as 'in progress'". What does that mean? Are you saying they have a "Status" of In progress or are you saying that the "Resolution" is set to "in progress". It would not make sense to have a value of "in progress" for Resolution. Please…

create a Dashboard and use the two-dimensional gadget or similar.

you can create an issue using the "+" and as long as you have the sprint field in the create you can add it there.

one quick thing that comes to mind that is often the culprit - Resolution field Look at one or more of those that are in progress and see what the Resolution field conveys. Is it Unresolved or does it have some value like Done? you might find this of interest

pulling this discussion back into context. Premkumar, please use the "reply" button when replying to someone rather than the "Answer" button. Epic Name is shorthand name for the Epic Epic Link is the name used to link a child (Story/Task) to the Epic. Here is a good read on this - epic-name-vs-epic-link If you wish to…

not to my knowledge but possibly for the very large customers there do. You can reach out to Atlassian Support (unless you are on a starter license which will lead you back to the Community). Note: I have never experienced an issue w/ the created vs. resolved chart and I have used for many years. This is not to say you are…

i was just checking the documentation and found the following so my previous response may be dated. Can you have a look at below and the docs? Note the above link is for Server 8.1 please be sure to select the correct platform/version for your instance.

in NG projects there are two rules (currently) that you can leverage for your board as shown below. Requiring a comment is not one of them. You are correct that NG is very simplified and that is one of the guiding goals. I do expect much more flexibility overtime.

First, to be clear, I'm just a user like yourself I guess. I do not work for or represent Atlassian so my opinions/statements are my own. The Marketplace, similar to Apple iTunes and Goggle Play are sponsored by Atlassian but the content is provided by third parties. I don't have any insight into any financial…

i don't have server so cannot test out the syntax. did you try using quotes as it mentions? "Epic Link" = DDMP-13 AND LinkedIssuetype=("is cloned by")

with JSD the user creating an issue is a Customer (user) so there is an address to send the response to. In JSW you have to set up a default user as the reporter of all issues.