Comments
-
Start at https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
They can make as many columns as they want. They can not (yet) group them as per the diagram above.
-
An Excel file is a pile of complex (potentially interacting) data that requires a complex editor to read and write. (To be fair, so is Confluence, which is why you can't edit Confluence pages in Excel) Importing the tables would mean copying the data from Excel into Confluence pages, where collaborative editing could be…
-
Wrong, it's not fundamental. But it would be useful. There's a request open for it.
-
The project templates are just templates, they create a load of schemes for the project you are creating. There is no reason you can or should not modify the created projects to suit you better. If you want an issue type of Story, go ahead and add it. Go to project admin and look for the "issue type scheme". Go into that,…
-
Collaborative editing is for page content, not attachments. To make it work for an attachment, you would have to re-implement most of Excel inside Confluence, than all the other editors for different file types. The only way to get close would be to import the tables you want to work on into Confluence pages.
-
How are you storing your "customers"? Off-the-shelf, you can simply use a custom field to do this if it's a known list, or set them up as users so you can use them in the reporter field or other custom fields. Or you could install Service Desk and use the "customers" and "organisations" in there. But I suspect there's…
-
Do you mean a java program external to Jira? If so, you'll need to use the REST API to call Jira functions. You don't need a lot of Jira knowledge here - create a java program like any other, and write REST calls in it.
-
At a glance, I see nothing wrong with Thomas' code. Where is it failing and what is the error?
-
I think you need to explain what this has to do with Jira (or other Atlassian software)
-
Yes, it changes the shape of the data. You can't just point a 7.7 at a 6.4 database.
-
That will happen already on screens where the issue type is presented. Fields that are not valid for the new issue type selected will vanish, and reappear when you change to a type they are valid for.
-
Matt is right, there is no "canned unassigned" user, it really does mean the field is empty. If it vanished, then my best guess would be an admin accidentally turned off "allow unassigned issues", so the option would have vanished.
-
I'd recommend a workflow change - when "rejected" transition is used, use "set field" post-function on resolution to set it to rejected. Then "project = NIM and resolution = rejected" will give you a result without you having to think about doing labelling or resolving it yourself.
-
Start at https://confluence.atlassian.com/get-started-with-jira-service-desk/get-started-with-jira-service-desk-917968272.html
-
You should generally switch off an add-on to test if it does what you expect, and then remove it if you know you don't need it. With the two add-ons you mention * Pages using the macro will work ok, but will just display an unknown macro placeholder for you to edit and remove or update it to another * The label tools are…
-
Use the actual project key, not the placeholder xyz. Try "NIM", as we can see you have a project with that key Also, do not assume "rejected" goes to rejected, it may be some other status.
-
If you need to edit the workflow for adding that transition or, you will need to work on an inactive workflow. See https://community.atlassian.com/t5/Questions/Can-anyone-please-tell-how-can-I-make-a-workflow-from-inactive/qaq-p/720547 which was for someone having a similar issue.
-
Ignoring the "done" column. Things in there drop off after two weeks.
-
The answers above are about doing it, and there are three ways to do it. Fields can be associated with different project/issue types by * Having different screens for create, edit and updating (screen schemes and transition screens) * Having different show/hide flags (field configurations) * Tell Jira to only place the…
-
No. A move is not a workflow action.
-
How are you "rejecting" them?
-
A view like this will not cause problems, as long as you only ever use it for read, and it doesn't put any significant load on the database. Upgrades may complain about it or even remove it, but you can put it back afterwards.
-
Does that error go into the log every time you try to do something? Is it always that error and no other? Could you have a look for : Errors in the logs that occur while Jira is starting - I'm looking for errors starting things Under manage add-ons, select the list for "all" add-ons (including system) and have a check…
-
I think I saw one for drawing the first ones out old style and then dropping any others that would have gone onto a second row into a drop-down.
-
An active workflow is simply one used in a workflow scheme that is currently in use by at least one project. To delete status (and do a couple of other things), you need to work on an inactive flow. The easiest way to do this is usually to copy the current one to a new name, as a copy will not be associated. Make your…
-
That was not clear in the question. I gave the correct answer for users thinking about direct access via SQL. I'm aware of how that application works.
-
I've got a cupboard full of backpacks and hoodies, plus 3/4 of my t-shirts are Atlassian or Adaptavist. I've also been able to attend Summits and tours at reduced rates (the last summit and the team tour tomorrow were free). So we do get some stuff!
-
You can't do this because you could put in restrictions that would prevent people from using the blueprint.
-
The template used is not stored by Confluence.