Phill Fox Community Champion

One potential add-on for this is Forms for Confluence which would allow you to capture any information you require on a page from a simple survey to very complex forms.

Hi Bevan From your description of your problem it sounds like the basic JIRA functionality will already work for you. You can tag issues and assign components as part of the creation transition. The area you need to look at is the workflow and in particular the different transitions. Many organisations apply a triage…

HI Dennis, I can see what you are trying to achieve here and it is certainly an interesting requirement for implementing an Agile board. One concern that I see is that you will have issues moving between boards as they are assigned to different teams which will lead to issues with reporting. In addition to your main filter…

HI Ravi, Yes you can but make sure you read and understand all the release notes for 5.6.x, 5.7.X as well in case there are any specific extra steps to take. Then follow the upgrade instructions at https://confluence.atlassian.com/doc/upgrading-confluence-4578.html Hope this helps. Phill

See the information available here. https://www.atlassian.com/university/certification/jira/exam-acp-100

When you imported the issues through CSV did you also import the attachment details? See the section on Importing Attachments on https://confluence.atlassian.com/jira/importing-data-from-csv-185729516.html which describes where to place the attachments for the import to work correctly.

Hi James, I think I see your challenge. You need to expand the list of Inactive workflows to find the Builds Workflow. image2015-11-30 18:54:22.png I hope this helps you if so please consider upvoting and accepting this answer. Phill

Thanks @John Paz looking back at my question I realise I was not entirely clear with my question and mentioned Bitbucket server when I was really referring to Bitbucket in the cloud. But very happy to push for both Bitbucket (cloud) and Bitbucket Server to be part of single pages as it would make life a lot easier. So here…

Hi Raymond Siebert Can you be clear on what you mean by associate a permission scheme with a user group. The way JIRA works is that permissions are set in a permission scheme which may make reference to various user groups and then the permission scheme is associated with one or more projects.…

Hi Venkat, You could use the component field for your list of features and even if you are already using this for another reason it is not too difficult to replicate its functionality using a customfield of type label. By using a customfield of this type you can then perform any queries you like to see which stories are…

Depending on whether you are working on JIRA 7 or an earlier version the approach is slightly different. For earlier versions you would do this through managing the add-ons and expand the details for the Service Desk plugin. With JIRA 7 this is done in the new section versions and licences page. More details available…

Hi Nicole I would approach this slightly different to your two scenarios (as I tried to explain in my earlier answer). I would treat each report as an Incident and create a Problem ticket from the first one reported and then link the other 2 Incidents to the Problem ticket. So you would then have. Incident 1 (Cust A, Org…

Hi Nicole Geske If you follow the ITIL principles then each issue submitted to the Service Desk is an Incident which will be resolved with an appropriate timescale. The resolution can be a simple fix, a workaround, a link to an existing known Problem or the creation of a new known Problem. I would use the two different…

Hi Flurin, You can add a number of technical and financial contacts to each Atlassian product who would then have the ability to manage the licence. I frequently recommend to customers that they set up an internal email group for this purpose as well to which all appropriate staff are added including at least one manager…

Firstly I would remind you that the aim of Agile is to support your business needs. So taking the new requirements as a business need means you need a process that supports this. Considering a "Scrum" approach with sprints which allocate a set period of time to complete a pre-determined set of activities does not readily…

An alternative answer is to consider what statistic is required. The reply by @Gabrielle Bautista [ACP-JA] tells you how many issues were created in a month and are now resolved it does not tell you how many are still open nor how many were resolved in the specific month. I believe a more meaningful measure is to know the…

Hi Padma, There are a number of solutions to your problem, here are a few for you to consider. * Create a set of template tasks in a project with all the common details that you require. Then using the issue filter select those which you want to apply to the latest module. Clone these issues and then link the new clones to…

Can you provide some more detail on what you are requesting assistance with so we may help you?

There were challenges with the release of the "Sprint permission" that mean that certain versions do not behave as expected. Can you provide the JIRA version number that you are on so we can confirm if that impacts you.

Hi Vineet Does this answer your question? https://answers.atlassian.com/questions/141766 If you are not seeing the editable field I would check that the screen is correctly assigned to the project. Are you able to edit other fields? If you are not able to edit fields then also check the properties of the status in your…

Hi @Celia Roser Did you check the compatibility of all your plugins before you attempted to upgrade to 7.0.5 there is a lag between new versions being released by Atlassian and some plugins being updated to match. For example a quick check on Marketplace.atlassian.com shows the Jenkins plugin is only supported up to…

You can find the version history of JIRA Issue Collector here. https://marketplace.atlassian.com/plugins/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin/versions This shows it was first available for JIRA iwith version 4.3 and was released 2011-09-20 As you state you are on version 3.13 you should review…

Glad you managed to sort it out. Importing a workflow with bespoke statuses would certainly cause challenges with knowing where to map them.

I would review the full list of statuses at https://<yourhost>/secure/admin/ViewStatuses.jspa -I am also wondering if there could be issues with accents? Or did you use the translate statuses option?I am sure Atlassian support will be able to quickly assist you in resolving this as they have probably come across the…

Hmmmm, this is getting tricker. And with the German names there are none that could be the same? I am also thinking here that accents on words may be ignored as well as the case.I would open the support.atlassian.com ticket now whilst we continue to troubleshoot so that if we fail to resolve then you are already in the…

Have you by any chance created a new status with the same name as an existing status but with different case? Eg "To Do" and "TO DO" or "In Progress" and "IN PROGRESS" or "Closed" and "CLOSED"?These would be what I would check for first.

Oh dear that is not very helpful at all. But help may be closer than you think.https://jira.atlassian.com/browse/GHS-11487 details exactly this error when a status was renamed eg To Do -> TO DO and the resulting conflict as some systems do not recognise the difference in case. Did you change the names of any statuses when…

Hi Vinzenz Mennicke It is certainly possible to use a custom workflow with an agile board but you need to do a couple of extra steps as well as creating a default board. On your board you need to go to Configure and map your new statuses to the existing or new columns. You may also wish to change the filter for your board…

Hi @Marla Landolt To edit a blueprint please refer to the instructions at https://confluence.atlassian.com/conf56/working-with-blueprints-658736938.html To create a new blueprint (including amending existing ones) see https://developer.atlassian.com/confdev/confluence-plugin-guide/confluence-blueprints If these do not help…

Calculated Number Field is not a standard custom field, so I suspect that you previously used a JIRA instance that had https://innovalog.atlassian.net/wiki/display/JMCF/JIRA+Misc+Custom+Fields installed on it. Although there are other alternative plugins that provide comparable functionality. It is worth checking your…