Walter Buggenhout Community Champion

Hi @Andrés Vallenas, Did you know you can use Epic cross project ;-)? My 2 cents - I would rather expect Android App, iOS App and similar things as components while Epics would be, well ... Epics. BUT (and note the caps there), I have little to no insight in your data. And if things are working for you the way you…

Hi Andrew, There are related feature requests for your question in JAC: - JRASERVER-18918 (for Server) - JRACLOUD-18918 (for Cloud) That does not guarantee that Atlassian will be providing this functionality anytime soon, but you can watch the issues to stay informed. In the meantime, be aware that you could already cover…

Hi @Guilherme Vieira, This is what issue type screen schemes are for. A good starting point in the documentation might be this page. In short, you will need to: * Create different screens for creating / viewing / editing each issue type * Create a screen scheme combining those screens for each individual issue type,…

No, you can't. The add-on is not available for Cloud. Cloud and Server are fundamentally different. See this related question for more detailed explanation.

Hi @Andrés Vallenas, I am afraid there is no silver bullet answer here. The main issue you point out here is that names are currently not readable in the backlog. As a rule of thumb, you could insist that the issue summary should fix that and have a clear and descriptive title, no longer than the number of characters you…

Hi Vlad, In the new UI, Atlassian made some major changes to boards. You can read a bit more in this article about that. A board is now associated with a project or - as you mention in this case - with the user profile of the board owner. As an agile board is a feature of Jira Software, you cannot associate it with a…

Great! Well done!

Best practice would be to use Project roles for this. By default, Jira offers a set of predefined roles, but you can extend this to match your organisation's needs (for more info, see Atlassian documentation). Next, you would assign groups (or individuals in rare and exceptional cases) to those roles at project level. Just…

No problem :-) - Feedback appreciated!

Hi @Bill Somerville, I'm not Atlassian, just a friendly guy trying to help you on how to turn off the design. The link is just called the way it is :-). Thx for giving feedback though, you triggered me to do the same thing.

Click your avatar in the bottom left corner and click 'turn off for now':

Have a look at the permission scheme and check the the settings for the Edit Issue, Add comment etc. events. If it states "Any logged in User", that might be the cause. 

Have you checked the new sidebar? And made sure you are looking at a scrum board (as a kanban board indeed does not have those reports)?

Yes. Locate the Issue type scheme in the Jira Admin section, click associate and then select the projects you want to associate it with. See instructions over here

Hi @Kote Khutsishvili, All you need to do, is associate a screen with the transition that holds the custom field you want the user to complete. For more info, see screen design documentation Then, add a validator to check whether the field is filled out.

I understand your initial disappointment and am sorry that you feel this way. As a last thing, I would recommend that in your search you still have a look into the linked issue option, as a small investment (probably no more than 1 day's work) in your workflow and SLA config and 1 or 2 simple automation rules will help you…

Go to project settings / people. On the right side, there should be a Remove option behind each customer:

Hi Mark, Thx for the clarification. Since Jira 7, permissions to Jira Service Desk, Jira Software and Jira Core are indeed managed through Application Access. For Software and Core, this is attached to having licensed access. On one hand, when you log in, you are no longer anonymous. And on the other hand not having…

You could also use the issue type Epic for your larger tasks, rather than create seperate Jira project every single time you need to complete more than 1 task to complete your mission. An epic is an issue type that acts as a parent to other tasks. These tasks don't need to be subtasks. It doesn't solve your numbering…

Hi Jozef, A first thing that might help, is the link Type that describes the type of relation. You could use e.g. different link types to make a distinction (e.g. "is parent of" vs "implements" vs "blocks" etc.). Scriptrunner (Adaptavist) is an app (previously known as add-on) with a lot of powerful JQL functions for…

Then again, If it is a must for you to track support in Jira Software, why would you even bother implementing Jira Service Desk? If I follow your story, you would only add the complexity that your Service Desk people need to move a ticket to the other system.

Hi Mark, It looks as though you are trying to bend your use case to the limits (and even over) the boundaries of the application. Instead of moving the issue to Jira Software, rather create a linked issue in Jira Software and use Service Desk Automation rules to make the Service Desk issue transition when the linked issue…

Once you connect a Confluence Knowledge Base to your Service Desk project, you will benefit from kb articles being shown related to the questions/issues your users type. For more details, see Service Desk / Knowledge base documentation. If you specifically want to open up a specific and static FAQ section to the portal,…

Hi Praveen, First check you Custom Fields configuration. Check out Field configuration schemes documentation and Custom field configuration documentation. The field configuration scheme and field configuration (especially the context) are key parts in determining visibility and the field being required or not across…

Hi Rich, Try Order by Epic Name instead. Be aware that you will not be able to reorder your stories on the board if you adjust your filter like that, as this requires your board to be ordered by Rank. But you should get the swimlanes ordered alphabetically like this.

Most likely, the 'Epic status' of the Epics is set to 'Done' (you can do that e.g. by right clicking the Epic in the scrum backlog and selecting 'Mark as done'. This makes them disappear from the backlog view, so you can focus on unfinished epics for planning. This related question gives a bit more background and also how…

Hi @Alexander Chemerys, As any IT team, you need to deal with a mix of planned and unplanned work. If you need to manage all of that with a small team of 7 superheroes, they will most likely be involved in both types of work. If you want to create visibility to both your team and your stakeholders, it is crucial to get all…

Hi @Ian Rees Log in as Administrator in JIRA, navigate to the Admin section of your JIRA instance (not Portfolio), locate the 'Add-ons' section. the quickest way to do this is just type g+g and in the dialog that appears type 'Manage add-ons'. It will bring you there right away. In the list of your installed add-ons,…

Hi @[deleted], Who are we to advise against a guy with inside knowledge of the app he and his team are going to build ;-). If the 5 epics you listed are the 5 main parts of your app, you are probably on the best possible track. You will be able to organise and track all work related to these areas in an easy, standardised…

One thing you might check, is whether all issue types in the project selection are configured in Portfolio's Hierarchy Configuration. All issue types you import, must be mapped to a hierarchy level. You find this in the Administration section of the Portfolio addon (In the JIRA menu: Portfolio / Administration and then…