Rik de Valk (Brainboss) Expert

Hi @Eugene Laarhoven , I'm not sure why you state that you can only use 1 component per issue. Could you clarify why? Because you can combine Components. Say for example you want to categorize your issues by color and by taste. In that case you could have a list of components that looks like this: * Green * Blue * Red *…

Hi @Anastasia Gourina , The Roadmap (/ Advanced Roadmaps) is the first feature that comes to mind. That gives you a nice breakdown of Epics and Stories.

Hi @Indi Petranek-McHugh , you can save a View so that other users an also switch to that view and see the same. But users can change their ordering and view settings after applying that view which will result in differences between what you're seeing and what they are seeing. However, once a use goes back to that View, it…

Hi @Rodrigo , If you have ScriptRunner, you could set up a behavior for that. If not: You will need to keep the Due date field on the Issue Create screen, but remove it from the Edit Issue screen. That prevents any user from editing the Due date field. Next you need to enable managers to edit the field. You can do this…

Well actually it does create the same hierarchical relation. But you can only really work with that relation if you also have Advanced Roadmaps, which is included in Jira Cloud Premium. Roadmaps are single-project. Advanced Roadmaps is multi-project and allows for more hierarchy above the Epic as well.

Hi @jeroen_wilmes , it is possible to have child issues across multiple projects. Otherwise cross-team collaboration would be super-inefficient. But if you create a child issue from the Epic view screen (by hitting the + sign) it will create the child in the same project as the Epic. So to create an child issue in a…

Hi @Robert Levine , You could do what @Eugenio Onofre suggests when you create a custom field 'Escalated by' of the type 'User picker'. But with your current set-up with the Text field, you will have to use the Edit Issue Action and then use a Smart Value to set this text field to: {{issue.assignee.displayName}} This value…

Hi @Albert Guite , If you go to Administration > Further Configuration, you will find the Site Homepage setting. There you can pick any Space to act as your site homepage (instead of the default dashboard. Have a nice day! Rik

Hi @Ann Rumenapp , A more out-of-the-box solution to your problem would be to track the project health in a separate Jira Project. There you can create one Issue per project and keep all kinds of attributes for these projects, including the Health (R/A/G). * You create a Jira project; Project tracker * You create an Issue…

Hi @Nishant Kant Ojha , you can do this using Smart Values. To give your new page the same name as your Issue Summary, you can use this: {{issue.summary}} For example, the below rule creates a page for every new Epic with the Summary of the Epic as the page title. You can read more about Smart values here:…

Hi, the docs from Atlassian provide excellent information including example code for Python: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get

Hi @Scott Buratt , On server or data center you can. In the System settings > Advanced settings you can find the parameter "jira.table.cols.subtasks". By default it will contain issuetype, status, assignee, progress But you can add your story point field. In my instance the Story Point field is "customfield_10019" so I…

@Nader_ Nadine _Consultant_ If I understand you correctly you want the users only to be able to pick form a defined set of labels. This is not possible by default. As always: there is probably an app for that 😊 I know that Scriptrunner for Confluence comes with a macro 'Add label' which allows you to define a set of labels…

Hi @Patty Land , this is a great question! One of the big dilemma's large organizations often face is the 'autonomy versus alignment challenge'. On one hand you want to give teams as much autonomy as possible, so that they can learn what works best for them. Let them experiment, fail, improve. On the other hand, large…

Hi @Jay , A team-managed project only allows you to choose for either grouping by sub-task or grouping by assignee. Sub-tasks will only show on the board if you choose grouping by sub-task. A company-managed project does allow you to do what you want. But as far as I know, there is no way to do what you want on a…

Hi @Rizwana_Firdaus , Tabs are not a default Confluence feature, so your Confluence site must be using some Marketplace App. If you can find out which App is in use, this will help the community to help you. Also, do you use Confluence Cloud or a self-hosted Server / Data Center version?

Hi @Cailin Che , If I'm not mistaking, the earliestUnreleaseFixVersion function is a JQL function provided by ScriptRunner. If that is correct, you will also have the issuefunction versionMatch which allows you to filter releases using a RegEx. That way you could at least find only relevant releases for 1 team using…

Hi @Paulina Mijal , the out-of-the-box post functions only includes the "Update Issue Field" post function which allows you to update some system fields (such as assignee, resolution, priority). * If you have JMWE (Jira Misc Workflow Extensions) you can use the "Set field value" post function to set a custom field using a…

Aha. The answer to that is simple, but not very satisfying: this is not possible in team-managed projects. ℹ️Currently, you can only create custom "standard" issue types. You can't create custom "parent" or "subtask" issue types.

Ah, it sounds like you're using XRay test management. If so, you can use a filter such as project = your-project AND type = Epic AND and "Requirement Status" = "v1.0 - UNCOVERED" But you should read the app documentation on this to get it exactly right: https://docs.getxray.app/display/XRAY/Enhanced+querying+with+JQL

Hi @Peuconomia Admin the Roadmap on Jira cloud doesn't allow editing the start and end dates of 'child issues' like you can do in Advanced Roadmaps in Data Center. You can only adjust the dates by assigning issues to a Sprint. The configuration of your Roadmap (in your Board settings) describes this in the settings: Child…

Hi @[deleted] , It is possible to assign the fixVersion via Bulk edit. But maybe you don't have the Resolve issues (which is needed to set a FixVersion) permission for all issues included in your bulk edit? Alternatively you can do it form a Backlog in a Scrum Board. Next to the Epic panel, you also have the Versions…

Hi @Satoshi Tobitsuka , it is possible to add and change issue types in a team-managed project. You can read about this here: https://support.atlassian.com/jira-software-cloud/docs/set-up-issue-types-in-team-managed-projects/ Kind regards, Rik

Hi @Deepak Sharma , If you want to find Epics that are not assigned to a release, you can use a filter like this: project = your-project AND type = Epic AND fixVersion is EMPTY Is that indeed what you are looking for?

I don't think setting any other fields is possible. Using the Issue Collector is probably the thing closest to a work-around. But it does require the ability to embed HTML / JS in the location where you want to have the 'link'. See https://confluence.atlassian.com/adminjiraserver/using-the-issue-collector-938847338.html.

Hi @ben , @Keri Savoca has written an article on how to do this. You can read it here: https://kerisavoca.medium.com/how-to-make-a-link-that-creates-a-new-issue-in-jira-54ff93c61e24 Have a nice weekend! Rik

Hi @Nicole Belflower , You can use the Browse projects for that. The title of this permission is a bit confusing, but the behavior is what you're looking for. If you assign the Browse Projects permission to Reporter and Participants they will be able to: * Find and access the project itself * View the issue to which they…

A Board will show whatever is included in the filter. So if you create 2 separate filters, but the filters have the same conditions, it will still show the same issues. So the first question you need to ask is: "What issue property needs to determine if it shows up on Board 1 or Board 2?" Maybe you want to base this on…

Well, the whole idea of API's is to enable you to fetch 'raw' data that you can than use to present it in a way that fits your specific purpose. If Atlassian would already present the data in a certain way, than it would be a lot more difficult for us data-consumers to freely use and transform the data to our liking. So as…

Hi @Абидин , Like @Dmitry suggested you can setup your Workflow in such a way that it is possible to transition from 'To completion' to 'Completed' but from 'Completed' back to 'To completion'. Alternatively you could a field that indicates whether an issue has been in Completed status. And set a Condition on the…