Oliver Siebenmarck {Polymetis Apps} Community Champion

Hi @Omprakash Thamsetty , I'm neither a Jira Server nor JSU expert, but if do remember correctly, not just any post function will work as a JSU precondition. You will need to use one of the two "Precondition…" post functions provided by JSU to achieve what you are trying to do. Beecom documented the way to do this here.…

Hi Simon, You are right: Labels in Jira are global, meaning that if you see some labels that you do not use in your project, they come from another project. That even includes projects you cannot even access yourself. This typically is not much of an issue if you are an admin and can do bulk updates on all issues in every…

Hi @Kamran786 , As you have noticed, the Copy from post function will always overwrite what's already in the field and it cannot take input from two fields. You will need an app to achieve this. I would recommend Cloud Workflows, because I work for that vendor, but there are other options as well. If you go with our app,…

Hi @Tim Purkey, The option to use and/or for conditions is a bit hard to find, but it's there. To find it, create the first condition and then in the view where you see all configured conditions listed, click "Add grouped condition" (i.e. the leftmost icon when hovering over your condition). The end result should like…

Hi, It'll be easier to answer this in depth if you provide more context, but let me try it anyway: 1) You want to use the REST API. There's actually two different pieces of documentation to look at, depending on whether you are on server or on cloud. By the the tag on your question, I gather that you have Jira installed on…

Hi Samuel, There's different ways to do this, but the easiest way is to group two "Value Field" conditions. To achieve this, create the custom_field_1 condition first and then in the view where you see all configured conditions listed, click "Add grouped condition" (i.e. the leftmost icon when hovering over your…

Hi Vithya, I am by no means an expert in either Groovy or ScriptRunner, but from what I can tell, your script gets all sub tasks and checks whether each one of the satisfies your condition, i.e. the if-part. As soon as one sub tasks does, it return true. Basically it checks if at least one of the sub tasks is of type…

Hi Nodar, You were almost there, here is the expression that should work as you want: user.accountId == issue.reporter.accountId || user.accountId == "1000a0000a000a000" The only two differences are that a) user must always be written in lower case and b) that the accountId-string must be in quotation marks. Hope that…

Hi Yael, While I very much believe that Jack is on to something, I can also see situations where you'd still want to enforce a rule. It could be that team members accidentally pick the wrong task, simply because they are unaware or anything else. Whatever the reason: yes it is possible to have such a condition on Jira…

Hi Ben, I believe the most straight-forward way currently would be to use the new "Project Automation" feature. To do that, go to the Project Settings and scroll down to "Project Automation". Using Project Automation you can define rules that execute some actions whenever a certain trigger condition is met. In your case…

Hi Hannes, The difference between Conditions and Validators did some getting used to for me, too. Here's my take on it: A Condition will hide a transition from the user, so that they do not even see that they cannot perform a specific transition. A Validator on the other hand will let the user see and attempt to perform…

Hi Robert, This is still simple in the cloud version, however you will need a different app: In my biased opinion Cloud Workflows is the easiest option, as it supports Jira Expressions as workflow validators. Jira Expressions are pretty similar to scripted validators, albeit with a different syntax. Your use-case would…

Hi Bryan, As Mohammed rightly pointed out, you will need to add a condition to your workflow. More specifically, you will need a custom condition as Jira does not offer this specific use case out of the box. While there is at least one other app out there, in my biased opinion Cloud Workflows is the easiest and most…

Hi Ken, That's indeed quite strange. Have you tried accessing the API without any credentials – that should yield the same results as the ones you are describing. If you are sure the credentials are correct, I really don't know what else to try. The API allowing for different levels of access for the same user would be…

Hi Ken, Technically, your curl command is correct and should return you the correct issue's data. The 404 hints at an authentication problem, i.e. Jira doesn't know who you are and will simply pretend the issue isn't there. So, I am guessing that there is an issue with your token. Also, curling…

Hi Michael, There are multiple ways to do this. Jira does include a condition called "Sub-Task Blocking Condition" which can block a transition if subtasks are in a certain state. However, I personally find it a bit cumbersome to use and also would rather have it as a Validator. (The difference being that a condition hides…

Hi Mark, This is indeed slightly annoying, but not unsolvable. Here's a workaround: Temporarily rename the status you are looking for to something memorable, "Sub-Task Done" for example. You can then easily find it in the list, add your condition and revert the name back to the original. Hope that helps, Oliver

Hi Rye, My reasoning was that the reporter always performs the create transition, thus pushing that issue to 'Open'. That seems to not be the case, and when I tested it last night, I apparently did so with an issue that been moved back and forth a lot. So, you're right, 'Open' being the first status makes it a bit…

Hi Rye, I believe there is a way to enforce this without installing any additional apps (although there are great apps out there). If I am not mistaken, you already have a "User Is In Group" condition set up. Additionally, you will need a "Separation of Duties" condition. This can be used to ensure that a user has not…

@Michael Arndt You totally can! The OR operator is || and it would look like this: issue.issueType.name == "Story" || issue.issueType.name == "Epic"

Hi Cristina, I don't think this is possible straight away. But the app Tempo Timesheets was written for this very use case. From my past experiences, I can very much recommend it. Hope that helps, Oliver

Hi Andrew, I'm afraid there is no out-of-the-box way to do this. Validators only act on workflow transitions, not on changes on the issue itself. Also, I cannot think of any apps that implement this behaviour. If you really need this, it should be possible to build something like this with ScriptRunner's Script Listeners,…

Hi Brian, Conditions are a workflow-thing that can be configured at many different levels. A workflow basically mandates how an issue can transition from one status to the next. Or in board terms, from one column to the next. You can think of the board as a visualization of your workflow. A condition manages what kind of…

Only way I could think of is first retrieving the accountId for each user using the '/rest/api/3/user' resource and then using that accountId to add the user to the group. That's an extra step for each user, but I do not think there is a way around this.

Happy to hear that it's working for you now! If I remember correctly, you can either use the accountId or the username. However, the preferred way is the accountId, because of privacy concerns, see also here: https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/

Hi Konstantin, did you base64-encode your e-mail:API-token pair? Simply copying the token into place should fail. Alternatively you could try by adding your e-mail and API-token directly to the URL, although that always seemed messy to me. Anyway, that would look like this: url =…

Sounds good, did you get it to work the way you want it to?

Ah, sorry I missed that part of the question. Two more changes should get you going. First, it has to be a POST request instead of GET. Rule of thumb here is: GET request will always just get some information, POST requests change things. Second, the group name has to be part of the URL. The documentation says so, but the…

Hi Sahana, AP.Request does not strike as the correct approach here, as that module is meant to contact the Jira instance your app is running on, not a third party tool like Salesforce. Also, you should check your Salesforce configuration. I might be wrong here, but I believe that Salesforce requires you to whitelist…

Hi Konstantin, The documentation can be a bit misleading. Unless you are using OAUTH, Bearer: <access_token> is not what you want to use. I suggest you try using HTTP Basic Auth, as explained here: https://developer.atlassian.com/cloud/jira/platform/jira-rest-api-basic-authentication/ Hope that helps, Oliver P.S. A similar…