Rik de Valk (Brainboss) Expert

Hi @Dorota NM , Just to make sure that you haven't overlooked this: The Spaces menu has a 'Starred' and 'Recent' section, but also a View all Spaces option. Have you clicked the View all Spaces option to see the complete list of Spaces? 

Hi @Fida Zubair , I don't think there is such an API response that includes the actual html link to an issue. You can however generate the link yourself easily using the construct {your-jira-base-url}/browse/{issue-key}

Hello @S S , using only a Jira filter you cannot group issues. You will need to use a Filter in combination with a Dashboard gadget. The filter you described can be used as the Filter. Now you create a new Dashboard and add a gadget to display the issues in a grouped manner. One gadget that comes to my mind is the Time…

I usually add a Project link to the Board so that you have an easy and quick link to access the Board directly from the Project

Hi, you'll first have to decide how you will distinguish issues from each project. Like Jose suggested, you could use Components or Labels. Once you decided what you'll use, you'll have to create a Filter. Go to Issues, search for Issues. Then create the filter. For example Project = MyJiraProject AND Component =…

Users without the Browse Projects permission on the project cannot see the project. So somehow this user will still have permission to browse the project. To troubleshoot this: * Open the project * Go to Project Settings * Go to Permissions > see which users and groups have the Browse Projects permission * Go to People >…

Hi @Shuky Afreen You can achieve this by adjusting the Default Permission Scheme by going to System Administration > Issues > Permissions Schemes (If your projects use a different permission scheme, you'll have to adjust that scheme instead of the default). You have to find the permission "Browse projects" and remove the…

There are several more factors that can cause missing issues. Number 1 is the Issue Sources. You need to make sure that the Issue Sources you configured contain all the issues. If your team works with 1 Board, this board can be set as the issue source. Next, all releases should be included. And in the last step of adding /…

Hi @Sindy Richter, Unfortunately, Epic is a hard-coded part of the Jira hierarchy. To apply SAFe in Jira, you need to consider Features as Epics. Renaming Epics comes with all sorts of trouble. So I recommend using a structure such as: Story < Epic < Program Epic < Portfolio Epic Or Story < Epic < Initiative A team level…

Hi @srinath reddy pinappu, Even if you've not applied any filters yourself, Portfolio automatically applies filters to your plan. These are Completion date and Schedule range. These filters limit how far back in the past and forward in the future the plan looks. You can read about these…

Hi @Arijit Koul, This could be caused by the Scheduled Range and Completed Range filters. At the top of the scope view you have some filters. One of them is Scheduled Range and Completed Range (or something like that). If that one is not showing, you can click on More to reveal it. There you can change how long in the past…

Hi Charu, You could use Tasks instead of Sub-Tasks and create issue links between the Tasks and Story. The Tasks can be in different Projects. Using the issue links, Portfolio will at least warn you about scheduling conflicts. 

Hi, like Nir suggests, you can use ScriptRunner. With Scriptrunner you can create a scripted post function in the workflow for Stories which checks if it is the last unresolved child issue and closes the Epic if true. However, bear in mind that users not always want to have the epic closed automatically. A better solution…

Hi Yen, Portfolio doesn't offer this feature. However, Jira offers something that might help. You can subscribe to your saved filter and get email notifications when new issues meet your filter criteria. You can configure when / how to be notified. For example: if you want realtime notifications for every single chandg. Or…

It's related to that. But not exactly the same. That ticket is about features that are / were missing for the Parent Link field. My issue is that the Parent Link isn't behaving the way it should. In my opinion it doesn't make sense that the Parent Link field is allowing closed issues to be selected. I've opened a new…

Hi Carl, To link boards to teams you must add the Boards as Issue Source. So it is not sufficient to have the projects as Issue Sources. The reason is that some data (sprints, velocity) is linked to Boards, not projects. So have you added the Boards as issue sources in you Plan Configuration? 

Hi, I read that Atlassian has published a work-around for this: how to set name and email as required fields. This work-around requires you to remove the name and email field form the issue-collector. But I guess this removes the fields from ALL issue-collectors on that JIRA instance. Can anyone confirm that? 

Hi, I have personally used the Excerpt and Excerpt include Macros to achieve this. It's not a direct solution; more a work-around. But it works for me! I simply enclose the Draw.io diagram in an Excerpt macro. After that I can include the diagram in any other page by using the Excerpt include macro. 

A Suggestion has been raised for this in October 2016. You can view it and vote for it here:https://jira.atlassian.com/browse/JPO-1681

If you have Portfolio for JIRA you can use the Team field in JIRA to create filters. You will have to setup Shared Teams though. You cannot use the teams you define within a Portfolio Plan.