Comments
-
We'd really appreciate a CLI – especially if it is scripting-friendly.
-
Hi @Takayama Shin-ichi (高山 伸一) , Welcome to the community! Out of the box, Confluence does not support mermaid notation. Fortunately, there is a wealth of apps available on the marketplace add mermaid charts and diagrams. Hope that helps, Oliver
-
Hi @[deleted] , Jira does not support nested projects – a project cannot have sub-projects. Having said that, if I understood you correctly then what you are asking is not all that uncommon. However, most organizations I've seen take a different approach; with varying degrees of complexity. The main thing for most of them…
-
Hi @Maneh Hayrapetyan , Out of the box, all labels in Jira are grey. If you would like to add a bit more color to your issue, you are going to need an app. In my, admittedly biased, opinion Colorful Labels is a fantastic solution. If you give it a try and need any help getting going, let me know: The team and I are happy…
-
Actually, I meant manually updating the field before replying to the customer, but I guess you could also try an Automation. First, the customer needs to have already been added to JSM – since you have the customer in a different field, you should be good here. Next, go to Project Settings -> Automation. Create a new rule…
-
Hi @Ahmed Safwat Marey , I would try this with Automation. Simply set up an automation in the slow moving project(s) with a Scheduled Trigger, run it every X hours and use this JQL to get all issue that have been assigned since then: project = "slow project" and assignee changed AFTER (-8h) Hope that helps, Oliver
-
Hi @Raoul Kaiser , You should be able to change the Reporter and set it to the customer. To me, that is be the most straight-forward way of handling this. Best regards, Oliver
-
Hi @Nathan Cano , Just adding on here, @Mikael Sandberg already said the important bit: Those colorful tags in the screenshot are epics, not labels. But, for completeness sake: you can of course put labels on issues and have displayed them on the board. Since an issue can only be applied to one epic, but can have multiple…
-
Hi @paul.bruillard , From what I can tell by looking at your examples, you are not doing anything wrong or differently then I typically do. Which leads me to believe, that maybe it has something to do with the central authentication. There might a global setting or policy that forbids API access, while I have not seen or…
-
Hi @Santy Balan , As far as I am aware, there is no way to do fuzzy label searches. As a really quick hack, you could try to leverage the label autocomplete feature to find labels that start with the same letters. Not sure if that still helps nowadays, but there used to be at least one label manager app for Confluence, so…
-
Hi @Morayo Bamidele , That does sound weird, but different teams have different ways of working so maybe there's a reason for why your new team has things set up this way. Still, let's look at how this might have been done: 1. Why is each board showing me a different backlog size Each board is populated by a filter (ie a…
-
Hi @Tobias H , Hi @Josip M The solution Alex showed indeed only applies to Company Managed projects. @Josip M , I believe you might be on a Team Managed project. It's hard to tell, but one of the many ways these project types differ is where the Epic's lozenge is placed on the issues in the background. In Company Managed…
-
Hi @Stavros Koureas , Welcome to the community! Yes, this is a common worry. We typically try to work around this by either requesting a larger amount of issues up-front or by carefully picking the order in the JQL itself. If you want to be extra sure, you can also enforce that the issue key or issue id is unique within…
-
Hi @paul stafford , That's indeed odd. I'm afraid, I don't know the app you are using (JMWE, right?) well enough to know what could be going on. You could reach out to their support directly or maybe @David Fischer has an idea of how to help you. Best regards, Oliver
-
Hi @paul stafford , Your Jira Expression isn't quite correct. Here's what should work: issue.issueType.name == "Bug" The issue object has an attribute called issueType which in turn has a name that may or may not be "Bug". The above Validator would only be true for issues of type Bug. Hope that helps, Oliver
-
Hola @Aldo Hoomz ! ¿Qué tal?
-
Hi @Umer Asghar , So sorry, I missed your question in November. @Bhanu KN is, of course, correct – Jira itself always links API tokens to specific users. While you can create technical user accounts for your integrations, that approach never quite felt right for us at Polymetis Apps. We therefore created an app for that:…
-
Hi @Neha Nadkarni Welcome to the community! There are actually quite a few label apps for Confluence Cloud, with differing feature sets. I can only speak with certainty on Magic Labels which has a bulk action feature that lets you add/remove/rename labels on all pages under a parent page – I like it a lot, but I also work…
-
Hi @olli_raatikainen , Welcome here! By now, you know that JQL does not have features like COUNT as SQL has. And you have also seen the dashboard work around @Rilwan Ahmed showed you. But what if you want to use the result more directly, say in a script or just want the number? Well, that's where Jira Expressions come in.…
-
Hi @Rey Joshua Macarat , Welcome to the community! Version 3 of the REST API is still in beta, it has been for quite a while. And a part of this beta API is an experimental endpoint to create a workflow. I believe that's the one @Paul Sorauer used when we wrote his original post. Since then, it seems that Atlassian have…
-
Hi @Gergana.Damyanova , As co-founder of a vendor who has an app for this in the marketplace, I really hope your team will go for the paid version. I vaguely remember you saying you're using Cloud Workflows – if that is correct you can also contact the team and me directly if you have any questions or concerns about the…
-
@Matthías Pétursson Glad you liked the Forge approach and got it to work :) But the invisible characters workaround is pretty awesome, wish I had thought of that.
-
Hi @Wroblewski, Arkadiusz , Welcome to the community! What you describe is really a two-part question: First, can you automatically update the Labels field depending on the content of a different field? Second, how to know what exactly to put into the Labels field. The first question is easily answered: Yes, that's…
-
Hi, Just a quick note to a great discussion: Labels are not case-sensitive, at least not on Jira Cloud. They can definitely be searched with JQL, updated with automation and do not have to become messy over time when used right. (And yes, I'm slightly biased pro-labels, as we have a label management app in Marketplace.)…
-
Hi @Matthías Pétursson , Hi @Philip Viningston , I did some digging into this a while back, but to the best of my knowledge, there isn't much you can do unless you get into client-side scripting with some like grease monkey. If you are really – and I mean REALLY, REALLY – annoyed by this, there is a work-around that I…
-
Hi @Colleen Gotling , So sorry for having seen this earlier. Since I work for a vendor that has a one of those Label Management apps in the Marketplace, this topic is very much close to heart for me. Unfortunately for us label aficionados, @Nic Brough -Adaptavist- is right: Confluence Cloud simply does not allow vendors…
-
Hi @Vikrant Yadav , Welcome to the future and to Cloud! I'm sure you'll find that it's great. As you might have already noticed, REST Authentication works slightly different with Jira Cloud. I'll try to give you the TL;DR version, but if you need me to go into more detail, just let me know. Basic Auth & API Tokens…
-
Oh, that sounds pretty cool! Thanks @Jocelyn Kim , I'll definitely check that out, too!
-
Hi @Schuuudi , I'm by no means an expert in Automation for Confluence, but I just cannot pass on a label-related question. That being said, I believe I know what happens. The Scheduled Trigger in Automation for Confluence runs without any specific page or space in context, basically meaning that it does not know which page…
-
Hi @Rithvik K , With Jira Cloud, API calls are always made authenticated, ie on behalf of a user. There is no general Jira API token with an all-areas-pass. However, people still want to build apps & integrations, so how to manage permissions? I've seen three ways how people work this in practice: Functional User Accounts…