Bill Sheboy Expert

Hi @Donald McKenzie -- Welcome to the Atlassian community! Are you asking about configuring swim lanes for a project board, or for a marketplace add-on Workboard? For a project's board, please select the ... at the right of the page, board settings, and then you will see configuration for swim lanes. For the marketplace…

Hi @Aniruddha Mallik -- Welcome to the Atlassian community! Please review this documentation for how to set the expiry for passwords for JIRA cloud: https://confluence.atlassian.com/cloud/password-policies-938859739.html Best regards, Bill

Hi @Scott Windus You are describing splitting the full workflow into the efforts of two teams: discovery/definition and delivery/release. As you want to implement these as Scrum teams in JIRA, consider that the work is different for the two teams, and so should be split into different work items. (This approach is often…

Hi @Raj Sidhu Boards are associated to a project, so select a project first and then you can select the board from the navigation on the left side of a page. To see all boards from that view, scroll to the bottom of the boards selector and select View All Boards. Best regards, Bill

Hi @DDL You can do this using the existing JIRA cloud features of automation rules, without the need to buy an add-on. For example: * Trigger: issue transitions (you can specify the status values, from/to) * Condition: matches the issue type you are interested in updating * Action: edit the issue type to the new value…

Hi @Mihail Turusov Short version is that you may need to experiment a bit with this... There are reserved characters that the split() does not like, but I have been unable to find documentation for the valid/invalid list. Perhaps they can be escaped, but I have not had success with that method. That is why I only searched…

Hi @Darren Bryant Yes, I agree that this reporting solution is not ideal. This is a complex problem for Atlassian to solve, as they need to roll-up information from the issue logs to compute cycle times, using dynamic option selection (time, status, filter, etc.). But they do not appear to have versioning for the workflow,…

Hi @André Valentin -- Welcome to the Atlassian community! According to a response from Atlassian staff on this community post in June 2020, there is no support yet for target branch in the smart values:…

Hi @Chau Nguyen -- Welcome to the Atlassian community! What help do you need, and what have you tried so far? Please consider posting the image of your rule so the community can help. An generic outline of what you are describing would be: * Trigger: whatever specific thing you want. For example, change of a specific…

Hi @[deleted] Short answer: you cannot do this exactly, but can work around it. Longer answer: When the issues are selected for a sprint and the sprint starts, the items are in whatever rank order they were in when added to the sprint. When an issue does not complete in a sprint, and returns to the backlog, it goes back to…

Hi @Anuradha Madhyani -- Welcome to the Atlassian community! I do not believe there is anything built into JIRA for converting, although the field handlers can be changed to use HTML rather than the markup. I am unclear on the impacts of that change. If you want to convert, please perform a web search and you will find…

Hi @Owen Dubiel -- Welcome to the Atlassian community! Returning to your original problem, once the issue is created in the VULN project you could simulate a move to the other project by clone and delete (or close). Then you can avoid the linking issue. Please see this documentation for a how-to:…

Hi @Julia Petrova Short answer is that you cannot do those things with out-of-the-box JIRA. Maybe there is a marketplace add-on that others will suggest. You can get the list of sprints for a specific project using the REST API:…

You are welcome! Please mark this one as answered so others can find the solution. Thanks!

I would make 3 different filters. That makes it easier to select them in the gadgets, and you could also set up subscriptions to schedule emails if some people would prefer a "push" rather than a "pull" of information.

Hi @Shahrukh Arif -- Welcome to the Atlassian community! The built in Rank mechanism in JIRA (called LexoRank) should be able to handle that ordering. Using something else may create side-effects and difficulties that Rank already addresses. If you are are making a dashboard view, you could: * Create three filters, one for…

That is interesting... When I use custom fields in smart value rule definition, I am able to use the human-readable name, rather than the custom field ID. Here is an idea: for an example issue that would not update, use the REST API to grab all of the JSON and confirm the field ID and existence. (This technique is also…

I am glad that helped you. Please consider marking this question as answered so others can easily find the solution in the future. Thanks!

Hi, Emilia. If the people you want to notify are watchers, you could try this one: {{issue.watchers.emailAddress}} As with the custom field, type that into the email TO field. I just tried it and it worked for me to notify watchers. I found that smart value on this documentation page:…

Hi, Maya! First thing, here is the documentation on advanced JQL, which may give you some ideas: https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-operators-reference-939938745.html Use this one to find the issues in a prior sprint and which are now in an open sprint: project = myProject AND sprint IN…

Hi @rupa_srivastava All of the fields may not be available for all of your issue types. * If the fields should be available, use the admin functions to update and make them available on screens and contexts. * If they should not be available, you will need to structure the rule to handle each issue type separately. For…

Hi Michael, What is the field type? I tried the following as smart values for text, number, and datetime fields and it worked to handle an empty fields as an empty string: {{issue.somefield|""}} When I exported the rule JSON, it escapes the quotation marks, so try that if entering the JSON directly: {{issue.somefield|\"\"}}

Hi @Gui Ávila No, I was suggesting that multiple selection works in the backlog view. You can use shift-click for a range or control-click for individual items. Once selected, right-click and add the issues to the sprint.

Hi @Maya.herman -- Welcome to the Atlassian community! The short answer is: you cannot do that fully. The sprint report uses current information in the issues and the activity tracking of the issues over time. You could create a JQL query to show the items that were in the sprint, but the remainder of the information would…

Hi @Amy Bass I think something got bent/broken in the trigger; maybe some regex stuff was added in the options. And your test condition appears after the action to perform the transition. Not sure what is up, so I recommend deleting that rule and starting over. Here is the example one I just created. The only thing I…

Hi @Emilia KASPRZYK Have you tried to enter the smart value in the email TO field? I found that if you type the field's smart value, e.g. {{issue.myCustomField}}, you will be prompted to enter the smart value. Just click on the prompt and it will add it to the TO field. Best regards, Bill

Hi @Valentin Plisson -- Welcome to the Atlassian community! According to the REST API documentation, this is how you get the standard and custom field list: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/field-getFields Best regards, Bill

Hi @Mihail Turusov I have not heard of NumberOfEdits before. Where did you see that one? Another way to count those URLs is using the split function and counting the list items: * Trigger: value changes for Description * Condition: If/else structure...* If the Description field does not contain https, set the count to zero…

Hi @Kanaka_Prasad If you bulk changed (moved) the story issues into epics, the summary field should be preserved. If you are wanting to bulk edit the epic name field, they would all end up as the same value, so it would be better to manually update 10 issues. Once the issue types are converted, you could perform another…

Hi @jira_admin_cu You could use automation rules to do those escalations of priority, if you have the automation add-on for your server instance. Please look here for more information: https://www.atlassian.com/software/jira/features/automation As an example rule, you would have: * Trigger: scheduled to run once per day *…