Ignacio Pulgar Expert

I'm not sure whether or not is better the way it works now, but I've just voted for it for Atlassian to review it, because if it used to work differently, it should now display a confirmation dialog informing that the subtasks are also going to be deleted as well.

I'd suggest contacting this plugin's support: support@gebsun.com Please note there are several open issues regarding this plugin's ability to hide time tracking: https://gebsun.atlassian.net/projects/HTT/issues/ By the way, while this plugin makes it easier to hide time tracked, there's also a native way to hide worklogs.…

It seems that the workflow transition between To Do and In Progress statuses has a post-function which assigns the issue to the user performing the transition. If that behaviour doesn't match your needs, you may edit the workflow and remove that post-function from the transition. Hope it helps.

I'd recommend researching a little bit on it and if, after reading the articles and performing some configuration changes the problem is not fixed, then you may open a ticket with Atlassian Support. Best regards.

Is there an email address set in the SD project for receiving email requests? If so, is it the same address configured in the mail handler? Also have a look at these articles:…

JQL can only return issues, and you can set it to show created date an resolved date. That said, you've got several ways to calculate the difference between both dates: * exporting the results and calculating the date diff through spreadsheet functions * use a third party plugin, like ScriptRunner scripted field for…

Also check if the user's email address is correct, as it might have a typo...

Hi Nick, As a site administrator, you can reset a user password by clicking on the user's username from User Management, then clicking on the Reset Password button from the top-right corner: If Jira emails are not being received just by one user, they are probably being sent to the spam folder, skipping the inbox. Make the…

Hi Haldur, First of all, I wouldn't recommend moving the issue from your SD project; the correct approach is creating a linked issue in the software project instead, after triaging it. If you remove the issue from SD, then SLAs won't be measured, and you will lose many of the built-in possibilities of Service Desk, like…

The question is unclear to me. May you rephrase it? Please, focus in what you want to get, and not in what you don't want to get. Providing an example may also work, and maybe a screenshot which clarifies what would you like the JQL to return.

Glad to help!

If you are on Cloud, then the button is like [...]. Note that the bulk change operation is usually performed after filtering the issues you would like to modify, so that's why it is reachable through the Issue Navigator, where you can type the JQL to get the issues you would like to modify. Regards

Hi Rena, The Bulk Change option is reachable through the Issue Navigator. Go to Issues > Search for issues, and click on one of the buttons from the top-right corner named 'Tools'. Hope it helps.

If you've sent the request, you'll receive a confirmation email in the following minutes stating that your ticket has been created. All you've got to do is waiting until Atlassian Support provide an answer. Note that only Atlassian staff are able to raising new Bugs in https://jira.atlassian.com/projects/JSDCLOUD Hope it…

Hi Rupa, I don't think there's a way to predict the exact performance improvement, as there are too many factors which might affect it (hardware, concurrence...). But the number of issues as well as the number of custom fields are known to affect performance, so do not forget to also delete any custom fields that do…

This answer doesn't apply to this case. I misunderstood the problem.

I've just understood the problem here! You were absolutely right; there's no way to open new Bugs directly in jira.atlassian.com so your response directing the user to Atlassian Support was indeed the right one. I've finally re-visited this question because of this other one rang a bell. Apologies for my misunderstanding.…

You should contact Atlassian Support instead of opening a new bug there.

Last Atlassian Bamboo promo video (kidding :oP)

Thinking of this as if it were a serious promotional video of Atlassian Bamboo. 

Fully agree on all those 10 points!

YW! By the way, you might also want to add jira-administrators group to all Global Permissions, if they weren't already set: https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html

Oh, I understand the misunderstanding. 😉 Kind regards

Epics is a good way to go, and has some advantages, specially if you need to report on a per week basis (Epic Report) and/or consistently estimate issues (sum up of story points per epic). Alternatively, and depending on your exact needs, you may prefer to configure several Swimlanes based on Queries, which would display…

On Jira Server, you can have the Text gadget at your disposal, which supports HTML content. Note that you might need to enable the gadget before being able to use it: https://confluence.atlassian.com/jira064/adding-the-text-gadget-720417086.html

Hi Walter, That's a good link to save as a favourite/bookmark. Please, welcome a little bit of well-intentioned feedback: Opening a ticket with Atlassian Support should be limited to issues with no feasible solution. In this case, it seems to be a lack of permission, which can be solved by the user, with a good pointer…

Go to the Permission Scheme of the project where you are trying to create the issue and ensure you get the Assign Issues permission (typically by adding your user account to the relevant roles in that project). Note that being a Jira Administrator doesn't mean you have all permissions in all projects. However, as I like to…

Exactly! You've anticipated my next comment ;-)

Hi Hector, May you possibly post here the formula you added to the description? I suspect there might be some html/javascript causing this. Maybe you can disable javascript on your browser, reload that page with Ctrl + F5 (for not using cached temporary files) and check whether that action causes the cog icon to appear.

Besides, may you go to admins Cog icon > Issues > Statuses and look for Ready To Verify? Maybe you have two statuses with similar names... therefore getting different results depending on the actual Ready To Verify status the query might be using.