Ignacio Pulgar Expert

Hi Júnior, A couple of questions: * Is the burndown chart set to be based in Story Points? * If so, is the Story Points field mapped to the Bug issue type through a context? Thanks and regards.

A couple of things I'd ensure all Jira Admins know in advance: * Custom field contexts * Global looping transitions Both features can save tons of time while keeping your instance in good shape.

If you think global looping transitions rock, please, vote for this suggestion so that all Jira admins can easily discover this feature while designing workflows.

By popular demand, I've edited the article by substituting the term reflexive with the clearer and most extended term looping.

Thank you @Rachel Wright ! It's an honor reading those words from such a reknown author! I'll feel the Force next month! :)

Hi @Nikhil_Gupta, The syntax specified by @Michael Wohlgemuth is the correct one. So, what you may need here is a more sofisticated JQL query builder, like this one I've just created for you. The cells that are supposed to be edited are the ones with light yellow background color. Multiple issuekey ranges are supported,…

Thank you all! @Daniel Eads I like the term looping transition. My vote for Atlassian officially naming it that way! 😃 @Antonio Ferruz Glad you liked it! 😉 @Fabian A_ Lopez _Community Leader - Argentina_ Florida_ California_ I enjoyed reading your articles too! 😊

Hi @Matt P! Here we are the promised article. The solution I was thinking of would be the last use case in the article, applied to the Priority of the Epics (see Use case: Edit permission on the field level), so that the Priority could only be edited by executing a transition. Add the post-function Copy field value from…

Hi Navin, This JQL returns all issues created more than 7 days ago and which are on the Open status: created < -7d AND status = Open For simplicity, the status condition could be avoided by using a normal transition from Open to Escalate statuses, instead of a global transition. There are apps which provide you with…

Sure! There's a good article about workflow properties here: https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status

The Destination field could be changed to a new custom field, created for that specific purpose, so that tasks could have different priorities than the epic they belong to. The workaround could be set in a quite satisfactory way, though it would require a quite long explanation. I'm thinking of writing an article about…

You can get all issues that do not contain the word 'Apple' by following these steps: * Execute the following JQL: text ~ Apple * Save your search as a filter, ie named "With Apple". * Finally, execute this new JQL: filter not in ("With Apple") After that, you'll get the list of issues that do not contain the word 'Apple'.

Hi Matthew, You're right; parentEpic does not support subqueries but just a CSV of epic's issue keys like: parentEpic in (KEY-1, KEY-2, KEY-3) There's no way to get issues belonging to a high priority epic by native JQL functions. Some workarounds could be designed, based on adding the following post-function (natively…

Hi Andreas, The benefit of having the possibility of adding external URLs to the issuelinks section consists of putting together all sources of information somehow relevant to the issue, displayed together. That way, you will always know what area of the issue you need to look for finding related info in a quick sight, no…

Hi Pablo, With no third party plugins, I'd suggest setting Sw Team as a required field for sub-tasks. If you're on a Jira Cloud instance, then a convenient post-function would be at your disposal: Copy field value from parent issue. You may use that function to automatically copy the Sw Team value on sub-task creation, by…

Here's mine: www.linkedin.com/in/ignacio-pulgar-0b72a757

Well done! Next-gen boards are different, yup, but you've solved it correctly! Just to keep in mind, boards can be created and stored in your user profile, with no need for showing them in the project's sidebar. Besides, it is possible to create a kanban/scrum board populated by project(s) of any types. More…

The only way I can think of would be having one board just for stories and a different one for tasks. Board's filters would need to be modified in order to filter by issue type accordingly. Hope it helps.

You almost got it. It is just a question of adding parenthesis in the appropriate places: ("Additional Assignees" = NAME OR assignee = NAME) AND resolution is EMPTY Hope it helps.

That kind of query requires the help of a third party addon like ScriptRunner, which enables advanced JQL functions like the one you need: issueFunction in linkedIssuesOf("resolution is not EMPTY", "blocks") Should you like to retrieve just unresolved issues blocked by resolved issues, then this query will get those…

Hi Eric, Yes, that's possible on issue creation through an automation rule. Note that more label conditions can be added as per your needs. However, I'd suggest to use Components instead of labels for this purpose, as components: * Are especifically designed for this purpose. * Do not require to create a custom automation…

A Quick Filter with this JQL can be helpful: type != Story Alternatively, the board's filter can be changed like this: project=KEY AND (type=Story AND status != <STATUS-MAPPED-TO-BACKLOG> OR type != Story) ORDER BY rank ASC

Sorry for my short answer. It was not intended to sound rude. Answerring from the phone just trying to be helpful. Kind regards

May you try typing "Issue Key"?

If you don't have any addons, then you do not count with the necessary tools to build a JQL query that can reference a subtask's parent status. In other words, you cannot set subtasks to disappear from your board once its parent had reached the status "Done" by any native means. That said, you may set a different trigger…

You'll need to count with Administer Space permission in the space from which you need to recover the page. If you have that permission, you will find a cog icon in the bottom-left corner. Click on it, and then you will find what you are looking for.

The external user would only be able to view those issues, and not any others in the project. Should that user enter the URL of an existing issue where the Invited Users field lacked her username, a message would be shown instead of viewing the issue, stating: "The issue you are trying to see does not exist or you do not…

Please, note that a Bulk Delete operation would be an exception and new issues would need to be created through the csv import. In this case, it would be appropriated to export all fields.

There's no undo functionality, but just a confirmation step were you can see the changes you are about to make. However, you may export to csv the issues returned by the JQL query with the Issue Keys, Summary and any fields you are about to change. If something goes wrong, you may reset the fields value to the previous…

If using up a license is not a problem, I'd suggest this solution: * Create a custom field of type User Picker (multiple users) and name it ie: Invited Users. * Add that field to the permissions you'd like the external user to count with (ie: Browse Projects) * Add the field to the project's screens. * Edit the issues…