Jeremy M Expert

Dear Andy, You are trying to change a Shared Filter that you are not the owner of, this is why the ''Save As'' button appears. JIRA will not let you overwrite the filter of a different user. If you want to change the filter itself, you need to become owner of the filter. Updating a filter You can update the name,…

Dear Guminukas, Some general rules for scaling which you might already follow, but to rule out certain problems that might exist; Regarding CPU usage.. much of the heavy lifting is delegated to Git. As a result, when deciding on the required hardware to run Bitbucket/Stash, the CPU usage of the Git processes is the most…

Dear Ola, Please see detailed answer below by Atlassian :-). Friendly Regards, Jeremy

Dear Ryota, That is indeed exactly why :-) Friendly Regards, Jeremy Mooiman

Dear Yasmeen, Correct, this is by design made that way. The ''Epic'' is always the highest point in the hierarchy. You could try creating a structure based on Issue Links and Automation.. or just with stories / sub tasks.. but a true Epic inside an Epic without tinkering is not possible and goes against the agile way of…

Dear Craig, Is it a possibility to restore the page to a earlier version? You can also manage your own drafts through your profile, and try out of removing cache works. Friendly Regards, Jeremy Mooiman

Dear Sue, So just to be safe here; You made a full XML export of the environment, and then imported it? Following this route; https://confluence.atlassian.com/adminjiraserver071/restoring-data-from-an-xml-backup-802592998.html#Restoringdatafromanxmlbackup-restorexmldata Friendly Regards, Jeremy

Dear Ashish, I understand. I am afraid that this is not possible for the Description Field, however.. based on your use case.. you could add additional Custom Fields which can store data themselves. What exactly do you wish to use this for, so we can think out a fitting solution. Friendly Regards, Jeremy Mooiman

Dear Adam, Aside from the points that Eduard gave, this can also be Cache related. Please check if all cache is truly gone. Friendly Regards, Jeremy

Dear Daniel, Have you thought about using Automation to set Issue Links on certain Issues when they are not set? This way you will not have to edit your JIRA in a way that makes using it difficult. Friendly Regards, Jeremy Mooiman

Dear Jai, Can it be that someone has disabled your access/permissions to certain repositories? Friendly Regards, Jeremy

Dear Peter, You can find a detailed example here: https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-a... Friendly Regards, Jeremy Mooiman

@Roger PorterI assume that the update functionality is not working. Could you check if your conditions match the ones that I have posted in my initial answer?

Dear Ryota, This depends, have you just copyed a certain Draw.io diagram from one page to another? Because once you include a Draw.io diagram into a page, it directs to one certain diagram within the Draw.io add-on. So, if you copy that imported diagram to another page.. it will still link the your old diagram. You should…

Dear Roger, When you head over to your project, to ''Users and roles'' and press ''Edit Defaults'' you should just be able to change the project lead. May I ask what browser and version of JIRA you are using? Also; How long is your project key/name? It could be due to this;…

Dear Aleksandr, When you edit a Workflow Scheme, you will see its ID in the URL. Friendly Regards, Jeremy Mooiman

Dear Ashish, Could you check the ''Automation Log'' when you create an issue? It should give you more insight into what exactly goes wrong. (For example, does your automation user have the correct permissions?) Friendly Regards, Jeremy Mooiman

Dear Ashish, Nopes, I am talking about the add-on; Automation for Jira by Code Barrel. This Automation module is alot more powerful than the standard JIRA automation. With the standard JIRA Automation you can also look for Issues with certain Components... although you will not be able to edit fields such as description…

Dear Ashish, Yes. This can be quite easily configured with; Automation for Jira You can create an Automation rule which does the following; When Issue is created, and component = ''Example'' then edit Issue Description ''Value''. Will be glad to make and send you an example. Friendly Regards, Jeremy Mooiman

Dear @Marissa Arrows I see! Well, I suppose that.. by now.. your problem has been resolved :-)? Friendly Regards, Jeremy

Dear Stefan, As for your first question; Sub-tasks come with an Issue/Story, they should be automatically included with your parent Issue. Why would you want them tracked separately? And for the reporting question; You could make a Issue Filter with JQL and put it on a Dashboard Filter Gadget; issuetype in (Story,Sub-task)…

Dear Mustafa, Like I said in my answer.. unfortunately.. you cannot see this right now. Friendly Regards, Jeremy

@Marissa Arrows No worries! Have you been able to fix it? If not, I will be glad to help you.

Dear yasmeen, I am afraid not; A sub-epic in that sense is a "story". You could add the Portfolio addon and use "initiatives" to group together Epics though - a layer above Epic rather than below. Or.. you could just add sub-tasks to the Epic.. but not an epic under an epic. Friendly Regards, Jeremy Mooiman

Dear Marissa, A board is available to all users who can view the filter on which the board is based. (Note that they will also need 'Browse project' permission for the project(s) whose issues are shown on the board.) To configure a board: * Select Boards > All Boards from the top navigation bar. * On the All Boards screen,…

Dear Mustafa, The query that you are using on the database will not work. When a question is deleted, the database entry will also be removed. The only way you can restore the answer is through a back-up. As for seeing who exactly deleted what, within Confluence as a whole.. this is simply not a feature within Confluence.…

Great! Thanks for the hard work to the team and to you, Monique! I am liking these new updates!

@Scott Grieder Good to see that it has been implemented! Keep going guys! Friendly Regards, Jeremy

Dear Susanne, Regarding to your question; Yes, it is possible to automatically close an issue after creating it. There are quite some options to do this, I will name some of the most widely used ones; If you have multiple workflow steps: Through Automation rules / Add-ons I am not sure about your scenario, but as for…

@Scott Grieder Awesome! Thanks to you and the team for the hard work! Interested to see the updates :-).