Comments
-
It depends on what you want from it. A condition stops a user using a transition. I can't really see that being of much help here unless you're expecting them to take a guess at the right value and manually set it correctly before then hitting the transition buttons A behaviour would be able to calculate a value for the…
-
Just to be clear, boards are not containers for issues. Projects are issue containers. Boards select a set of issues to look at. To "put an issue on a board" is nonsense really, what you have to do is give the issue data which causes the board filter to select it.
-
You can't, it's hard coded at the moment. There's a request to be able to alter the units open with Atlassian.
-
Check the settings for Synchrony and Confluence as well.
-
No, you really don't want to do this, it makes a total mess of your project. It inevitably leads to "I thought someone else was doing it". Keep the assignee as the single point of responsibility for an issue, even if it changes a lot. If you need to associate other people, then use a custom field to represent "other people…
-
I'd use ScriptRunner for Cloud (as you'd expect from someone who works for Adaptavist).
-
That's correct, a sub-task is part of a story and hence goes into a sprint with its story. A story, logically, cannot be complete if it has open sub-tasks. So, it's nonsense to have open sub-tasks on a complete story. If you do find yourself wanting to do this, then either move off Scrum (because you're not doing Scrum),…
-
Go into each project your board includes, and check the permission scheme. Make sure your account matches the rules for "project administration". Most of us use roles, so you will probably find you need to make sure you add your self to each of the project's "admin" roles.
-
It's because your code is trying to do the wrong thing. A cascading select list in Jira is a field similar to select list, albeit a bit more complicated because of the option-pairs, but the data and options are roughly the same principle. The value you set in a selection is an option, one drawn from a list of pre-defined…
-
You'll need to ask ResearchGate - we're end users of Atlassian stuff here, not the admins for your system!
-
No, there is no "other" way, because the way you do it is immensely simple and there's no need for other methods. All you need to do is install the two services separately - make sure they use different directories, different database areas and ports, and that should work fine. The defaults generally work ok for this. So,…
-
What have you set their allocated memories to? Look for the Xmx settings for Jira, Confluence and Synchrony (if you've got collaborative editing enabled). You need to give all of them a maximum limit for their memory, and allow room for the operating system.
-
No, CSV imports are built in.
-
ScriptRunner for Cloud is available. It's not the same as ScriptRunner for Server, as Cloud limits what you can do a lot more than server.
-
In the global permissions, allow anonymous access. In each space permission, allow anonymous "use" but not "create/edit" - you'll be able to see how it works just by looking at the space permission page.
-
No. Multiple status for an issue is nonsense, or at least something you should not do with workflow because in process terms, it's nonsense. You can't have an issue that is both open and closed at the same time - our time-limited human brains simply can't work with that. Transitions can only have one end point as well.…
-
Confluence is not a Jira application, it's another service.
-
Some of the system "importers" do that, but they're mostly only available for Server and they are not generic, they're for importing from other issue trackers, so they expect the database to be in a very specific shape. Your best bet for Cloud is to extract the data into CSV and import that
-
It looks like you need another read through https://developer.atlassian.com/cloud/jira/platform/getting-started/
-
There is no "plugin install". Start simple. * Jira Core is a "platform" for other Jira applications and add-ons. To get Jira working, you install Jira Core. This provides the basic structure for everything else, so you get projects, issues, fields, users, workflows, and a server platform you can add other things to. You…
-
Code. You need to do one of: * create reports that can find your issues * write JQL functions that can look for it * create standard custom field and write code to populate them with the closed date * write scripted or calculated fields that can go back into the history and look for the dates you want
-
What columns are the stories in on the board?
-
That's simply a custom field your admins have added to the request forms. Your admins can change it in the project config.
-
Yes, the user can fill it in on issue creation. You can make it mandatory too.
-
Have you checked the baseline permissions too? Also, how does this manifest? No buttons, or nothing happens when you click? Is it just that one status in the flow? Can other people edit or assign while in that status?
-
Put the field on the Create screen, but not edit.
-
Yes, although this simplifies your choice, as ScriptRunner for Cloud can only give you the post-functions (i.e. calculate as it goes through the flow)
-
Click on the status when editing the issue and look for "properties"
-
I'm not sure what you mean by "Service Type" - Service Desk requests? Or the system services? Are you on Cloud?
-
Where are you seeing this error? On-screen or in the logs?