Daniel Ebers Expert

Wow, this came unexpected. Let's focus on the first screenshot. There is clearly missing the restriction as to the usual "one week looking back" period of time. Or, in other words, Jira behaves correctly - as there is no time selection in the query. I have never seen such. How come this part of the query is missing? Now…

From your description this indeed corresponds with the Suggestion as well as the App.

Using Automation I built you a rule the following - it is tested and works fine. But this would need to switch to Automation. The rule triggers on commenting your "main" issue and checks if ALL linked issues are in status "Done". If so, the "main" issue (the one which links all other issues) is transitioned to done, too.…

Some very basic question - but the best guess to get to the bottom of the case if you allow. * Could you please check for "Updated recently" if the JQL query indeed expands to: updated >= -1w order by updated DESC (you can switch to "Advanced" mode and it will show you the JQL) * If so, could you please check in history…

Hi @sanjay there has been a Suggestion in the past which is meanwhile closed using status "Won't Fix" but from there an App was suggested which is reported being capable of what you require. Please double check the Suggestion for all further information: * Restrict Attachments Based on File type…

Awesome, great to hear it is working now - yes, please update us what you find out, I am all ears. Thanks in advance!

Another question that comes to my mind - far away from mail handling as such... is there some kind of validator/condition in your workflow that could prevent the opening of a new issue via mail (f.e. transition restricted a specific individual)?

I pasted in a link in the answer above - you fill out a form and get a reply. https://support.atlassian.com/contact

Hi @Raj Prajapati there is no support here - this is Community where users help users. This topic seems to me being full of more specific questions which you could direct to Atlassian Support - if an upgrade did not help. https://support.atlassian.com/contact Regards, Daniel

I believe the nearest of what you describe is the HTML links feature that is available from Jira Server, but not Jira Cloud. https://confluence.atlassian.com/jirakb/how-to-create-issues-using-direct-html-links-in-jira-server-159474.html Based off your explanation this is 100% what we did in the past for a requirement like…

There has been some discussion around it but a reporting from database seems not feasible. I linked the discussion above for you to better understand what is given currently and what you could probably consider next. By no means it will be an easy task to do. Even if this succeeds, if won't mean that it works after a Jira…

@Colby Knight In case you should need the documentation on what Brant suggested you can find it here. The "engine" by means of the logic, needed for Jira to execute what is desired, is the JQL query of Adam. Bringing those pieces together you will be able to reach your goal in no time. * Working with search results…

Hi @Pritesh Gohil, the text "Refresh to see summary" is defined in the corresponding request time of your Jira Service Management project. Given this is a classic Service Management project please navigate you your project then Project settings >> Request types >> Request form There you will see the field Summary in…

Glad you have fixed it :) I am just an user trying to help here in Community with some ideas - thanks for your nice words! If you don't mind - please please click "Accept answer" - other users with the same question can then find an answer to the same question quicker. Many thanks in advance!

Hi Jonathan, the filters cannot be disabled at their place in navigation (where you seem them). For a deeper understanding on what is happening here a knowledge of how you handled the issues would be necessary: * By a JQL query: which "updated" timestamp does the issue (for example) D2-4 show up? * between D2-5 and…

Hi @Maciej Wrześniewski welcome to the Atlassian Community. Reading your request this is what "Issue Collectors" were made for. You can use them right away from your Jira Cloud instance - no additional costs. https://support.atlassian.com/jira-cloud-administration/docs/use-the-issue-collector/ Some more complex…

Hi @Mikaela Thorén I could imagine the field is "hidden" (option: Hide) from the corresponding Field Configuration Scheme - have you checked this already? Apart from that you could use the "where is my field" helper - this normally explains pretty good why a field is missing. Cheers, Daniel

This is strange, indeed. The last idea that would come up is to have a view into atlassian-jira.log if something meaningful is logged the moment you open a backlog. In case this brings no enlightenment I'd suggest waiting if other Community members can bring up an idea or to raise a request with Atlassian Support.

The content should stay like it is but tagging (mention) is not possible anymore as far as I know - but please double check.

That depends on if you are on Server or cloud. Also there is some Suggestion open with Atlassian which might prevent re-used even if the project was deleted (at least if there has not changed anything recently - as stated above).

There are solutions available from marketplace like Group Sign Off and others which are capable of a broad range of such feature - but I cannot say for sure if every aspect of your requirement can be met (I haven't tested it). Most likely you would be able to implement parts with it, and garnish your process with some…

There has been a discussion on this back in October - at least it comes very close to what you are experiencing right now. The summary was that it is not possible to create a sub-task directly under an Epic but in case moving parents it can trigger such behaviour. Changing Issue type apparently is also capable of doing so.

Two ideas that come to my mind: * please check if some issue was assigned to the sprint outside a possibly present Kanban/Scrum board. This could have happened directly in the issue assigning a sprint (a JQL query for the sprint itself should clear that out in no time) * please check if there is another user with the very…

An option (or addition of some kind) could be to work with components. They bring an built-in option with them to assign Project Lead. From what you described you are not goint with components right now but a custom field - if this can be changed it would be possibly easy. If not some combinations of several methods could…

I agree with Liam. Although not familiar with Mimecast service from the looks it should be possible to release the mails held back (see "release" from the mail you got / or even the "permit" part). For further diagnosis I suspect the best idea would be to speak to the person who set up the mail service for you.

Just some questions: 1.) did it work in the past or the mail handling a new setup for this instance? 2.) you mentioned you had an App in place supporting incoming mails - is this meant in general or was on this instance the App installed what now could result to some kind of interference with your new configuration? 3.)…

Hi @Anna Dannheisig I am wondering if this could be some kind of browser related issue. Did you try to open the backlog view in an incognito window of your browser or even in a different browser (for a short test)? Regards, Daniel

Awesome! That's great to hear!

I try to get some help. Please post back here in 2-3 days in case you did not receive feedback.

You are trying to create an Issue Type from your screenshot instead of a Request Type. Please kindly refer to the documentation I linked earlier.