Thomas Schlegel Community Champion

Are you sure, they were not flagged before and you just did not recognize it because it was not so "visible" on the view? You can see updates on the flagged-field in the issue history. 

You can query for flagged issues with this JQL: flagged = Impediment

Hi @Maik Erler , an issue is flagged, whenever you flag it. There are functions in the "..." - menu: Add flag and remove flag. A flagged issue is highlighted on the board, so you should flag your most important issues.

Hi @Felix Le Goffe , as far as I know, you can only import Word documents. Maybe you can transfer your pdf somehow to the MS word format or attach the pdf to a page and use the pdf macro to show the content of the pdf on the page. 

Hi @Claire Cuthbert , could you please post your exact queries here? Maybe we find the issue when looking at your queries.

Hi @edwin , what do you mean by "mother template"? There's no such thing in Confluence.

Hi @abir_ayadi , I've never heard of something like this. You can change the color in general with CSS like it is described here: https://community.atlassian.com/t5/Confluence-questions/how-can-I-change-page-tree-colors/qaq-p/618573 but not conditionally depending on the content of the page.

No problem, Adam. Have you tried the query status != Done OR status changed to Done after -7d ? This really should give you the result you are looking for. Once again: which issues are missing? We're running in circles, if you can't say, what is actually the problem. I'm heading home soon, so I'll probably answer again…

Do you want issues which were closed in the last 7 days (as you described in your first post) or do you want issues which were created in the last 7 days (as you described in your last post). I don't want to be annoying, sorry for that - but I'm not quite sure what you want to achieve and which issues are missing when you…

Thank you, Adam. I think, your JQL should do exactly what you describe - if your closed issues have a resolution. If not, this might be the problem. You can replace "resolved >= -7d" with "status changed to Done after -7d" - maybe then the result is correct. But if it is, you should have a look why your closed issues don't…

Hi @Adam Taylor , so sorry, but I don't understand the problem. Isn't that the result you wanted to see (every incident that has been closed within a 7 day period) ?

That's an unbalanced deal, @Max Foerster - K15t , "Lord of the Rings" is six times "Bridge to Terabithia" ;-)

Thank you so much, I'm so happy :-) - and congratulations to all the others and thank you everyone making this community such a great place. It's not only these award-winning people which makes the community, it's every single one of you. 

That's what I described. If you select both filters, you will only see issues which have both labels, B and C. You don't see any issues which have only one label. If you want to see issues which have label b and issues who have label c, create one single filter with a query like this: labels = B or labels = C

Hi @Moto Bro , do your issues have both labels, B and C? Filters are always additive, so if you enable both filters, you only get issues wich have both labels, B and C.

Hi @Shaun Parker , no, you can't use a project-key for a second time. If it was used once, it can never be used again. Even if the project key changed to another key in the meantime.

Hi @kirk senkowski , please contact Atlassian Support here: https://support.atlassian.com/contact/#/

Ah, great, @Bill Bailey - I forgot about that already... 

Hi Summer@69 , you can create an additional custom field for that, but why do you want to show this number? The backlog is meant to be ordered by priority - the highest priority is on top of the backlog. Just move your backlog items to the right place and start processing them from the top of the backlog.

Are you able to add a page in that space? The Import Menu Item is not available, if you don't have the edit page permission.

Agree with @shetty , I would never ever use the same name for a Standard Issue Type and a Sub-Task Issue Type. You will totally confuse your users with a configuration like that.

Hi @Bettina Kugel , it should be there:

Hi @Tiffany Lirones welcome to our Community! Besides technical questions or discussions, have a look at our Friday Fun posts. You can still comment on every single one of them. Or join some of our groups. Hope you like them. 

The first book, I read by myself when I was six years old was "Mikosch, der kleine Zauberesel", a book about a speaking, magic donkey. I read this over and over again. For sentimental reasons, I ordered this book some years ago from a second hand book store, I don't have my old copy anymore. Then I read tons of a book…

Hi @Raphael Soares , there are no further levels than Epic - Task - Subtask. You can construct something similar with links, but this is not the same as a real hierarchy, it's just a link then. With an app like "Structure" (there may be more, but I know this one) you can create a structural overview (as the name says) with…

Hi @Anas Ibrahim , we also use the free app Multivote: https://marketplace.atlassian.com/apps/1210786/multivote-for-confluence?hosting=server&tab=overview

Remove the Swim Lanes, with Swim Lanes, this will never run. An issue can only be once on the board, not twice or more times.

Hi @Reshma Regi , there's no issue field security in Jira. Security is based on the issue, not on a field. There are some apps for that purpose, but I can't recommend one, because we do not have any of them: https://marketplace.atlassian.com/search?product=jira&query=field%20security

Or create four quick filters, if you want to keep one single board: component = Producer component = ... So you can filter your issues with these filters.

What was the problem with the four boards, one per component? That's the way, I would do this. Create four boards with a query like project = ABC and component = Producer project = ABC and component = Trucker project = ABC and component = Web project = ABC and component = Technical And then the issue should be on your…