Comments
-
That's up to your browser, not Confluence. You'll need to configure it to automatically unzip, check what's in it, and then run up the IBM Data Studio if appropriate.
-
Yes, they have been diverging significantly for a long time. Cloud has a different UI, Next-Gen boards in Software, business boards in Core, a new issue layout, and and and.
-
You can almost change the condition straight into a validator, making sure the fields you want to check are on the transition screen. Then, when an issue fails the validation when someone tries to move it, they will be returned to the transition screen with an error message.
-
A board is not a container for issues, it is a view of a set of them, so you do not "move a card from one board to another". Because they are a view, when you configure a board in one way, it is going to display all the issues it selects in the same way.
-
To do this, you need to ensure the new database is an exact copy of the old one (i.e shut down confluence and then duplicate it), then you can edit the confluence.cfg.xml file to change the url.
-
Broadly, yes, I think you can see how to use other fields in there.
-
You asked to get the value into a field. Do you mean you want another sprint field? That would be a bad idea for your users, and you'd rapidly run into problems with volume unless your code was able to dynamically select during issue create/edit
-
What do you mean by "access"?
-
It's a field set by an App, it will populate naturally when you use the functions of that App. Tempo is my guess, unless you have Portfolio. Unlocking it would not let you add values anyway, you have to go through the App.
-
This is not a good way to report on this. The Jira database is not built for reporting and you will quickly find yourself building complex, expensive queries that are slow, probably inaccurate, and stress your systems. Please, do this properly and ask Jira for the information over the REST interface. Or better, inside Jira.
-
No, I'm afraid they've moved into a drop-down and there's no way to get them out. Improvement requests have been raised with Atlassian to get them back to somewhere useful.
-
Yep, and that's 10-11 attachments and your 25Gb is gone, then another 30-40 and you're over the upper limit.
-
No. You have to have transitions to enable status change. It is not a "field", it is an indicator of the position and path through the workflow. You can only change it with transitions.
-
For the "set", see https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/postfunctions/set-issue-attributes.html For a get, I've got this saved def sprints = issue.getCustomFieldValue(ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("Sprint")) Note that I use "sprints" because an issue could…
-
You don't appear to be using a set in your code. When you do, https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/postfunctions/set-issue-attributes.html is a good bookmark for sample code.
-
That's correct, you need something to distinguish between the issues so you can separate them out between boards. A custom field is a good option for doing that, and "topic" sounds like a good name for it in this case! And yes, multiple boards can work really well. If you have "one board per distinct topic", or you have…
-
I am sorry, but that still does not help. "plugin count versions requirements bugs" is still just a fragment without context. Best I can do with that is tell you that you can count the plugins by reading the "system information" or "manage add-ons" pages in the admin section. The rest makes no sense.
-
That's a poorly written phrase which suggests boards might be containers. This is wrong. I would have written something more like "A quick link to create issues from the board" Especially as you could create issues that do not go into a board (For example, if you have a board based on "label = x" and you don't put label x…
-
I am afraid a fragment of a sentence that just names different bits of a system without any context is not something we can work with. Could you try writing this as a question please? What are you trying to achieve for your end-user? What have you looked at so far? Where are you looking?
-
Boards are not containers for issues, they are a view of a set of issues, and that set is selected by a filter. There is no "issue belonging to a board" - an issue belongs to a project, and is then chosen for inclusion on a board. You don't need to set up "a filter that shows issues belonging to a board" - the board…
-
It looks like they probably found the firewall and opened the right ports.
-
NEVER write to a Jira database with SQL, unless it is offline and you know exactly what you are doing (99% of people trying it do not know enough to risk it). Otherwise you will damage (potentially destroy) your system. That change almost certainly is the problem, and you really need to undo the damage. Ideally, restore…
-
Um, add multi-user-pickers and/or group pickers to show "other people who may be partially responsible" Do not try to use this instead of assignee, it should only complement assignee. You will end up with people complaining about issues being ignored (and I've lost count of the tens of thousands of issues I've seen…
-
You don't. If you find they are being recreated by Confluence after deletion, then it's because Confluence needs them for some reason. No harm in deleting them (when Confluence is offline), but it's creating them because it needs to. You could see if increasing memory reduces the volume, but that's about the only thing you…
-
>I am trying to show the whole board to all users with the issue names, I just dont want them to click on any issue and view. They should only be able to open/edit the issues created by them. This can't happen, because it makes no sense. You need to decide whether a user can see an issue or not. If they can, then it will…
-
No, the software is intended to tell everyone about all systems.
-
No, because each App has different ways you might measure usage. An App providing a workflow condition could be said to be "used" whenever a user looks at an issue. For a post-function, every time it is run in a transition. For a report, when it's hit by a user (this is not recorded unless you set up additional logging).…
-
No, once the logs are too old, they're gone.
-
There is an audit log which includes deletes under the admin section.
-
But you're not a Jira administrator, as I said you need to be.