Comments
-
When you are in the screen that configures a script, there are two boxes. A large one for writing the in-line scripts, but also a single line for a script location. The script location points to a file on the server's disk, usually under <jira home>/scripts - I keep all my scripts in there, under source control.
-
There's nothing worrying in that log, could you try the application log as well? <jira-home>/logs/atlassian-jira.log
-
I think you need to forget the global permissions, they're confusing you. When you need to have someone see issues in your project without logging in, grant "browse" permission to the "group" called "anyone" in your project permission scheme. I would strongly recommend that you do not grant "anyone" anything other than…
-
:-) It's quite an acquired taste, but it works for me. And that's why I always say, 'Shumshumschilpiddydah!'
-
That's not a standard thing in Jira, so my guess is that your Jira has been set up with a customised workflow that has a "waive" transition in it. If you do not see that transition, then either someone gave you the wrong guidance, or you do not have permission to use it. I would ask the project owner/admin to advise you on…
-
You'll need to do some coding in Excel - it should be possible to write scripts in there that can fire off a REST call to your Cloud Jira to cause the creation of issues. Your scripts can look at many sheets to gather together the data to send.
-
How are you trying to add this app? You seem to have landed on your my.atlassian account, which is not where you'd normally install from.
-
Cloud's Connect framework does not yet allow for apps to handle conditions and validators
-
Cloud's Connect framework does not yet allow for apps to handle conditions and validators.
-
There's not a lot more we can tell you than what the error message says. The Jira server is not able to reach the database server or is being refused access by the service. How have you checked the things listed?
-
That version is old and unsupported, and I strongly recommend you upgrade to a secure version (4 has security problems which will never be fixed) There are a couple of add-ons for that version which do SLAs, but the best option is to upgrade to a version of Jira which supports the full Jira Service Desk functionality.
-
Yes, if you install Jira Service Desk.
-
Simplified workflows do not work that way. All you can do with them is add status, and map them to columns on the board. If you remove them, the status remains on the global list. There's no backup copies or inactive access, you only get to amend the workflows. You should ask an admin to tidy up all your unused status and…
-
You have somehow managed to delete a screen that your workflow was using. Edit the workflow, find the transition, and change to another screen (or remove it)
-
If the account is a customer account, no, they are free. If you add them to any of the Jira "can log in" groups, so they can use Jira as well as the portal, then they do cost, as they're now a Jira user.
-
You can attach them to pages, but Confluence won't read them. They're not in a format useful for conversion to Confluence pages.
-
Mildly annoying that Confluence doesn't have an .rtf importer, but there are loads of free utilities that can (bulk) convert rtf to doc. Have you tried that?
-
It's the same answer as above - you will need to consult the docs for whatever your 2FA system is.
-
There isn't really anything to "solve" - your code is trying to use functionality that simply is not there. At this point, it would be better to revisit the requirement and see what you might use to do it. In your original question, you pretty much described the behaviour of a cascading select. Why are you not using one of…
-
I am afraid a string of unsorted words with no explanation or context does not tell us anything. If you need help with something, you will need to explain what you are asking.
-
Have a look at https://confluence.atlassian.com/purchasing/how-do-i-add-or-decrease-users-321257597.html
-
What app are you using to provide the regex?
-
The Jira toolkit add-on has a field that can expose user properties to non-admins. I'm not sure it solves your problem, but I think it's the closest you can get without writing something for yourself.
-
Someone just reminded me. If I'm going to choose a proper superhero, rather than characters I really like, it's Dr Manhattan, because his main power is "omnipotence"
-
I don't think you have understood the analogy. People who (genuinely) like their own pictures on Facebook are seen as "losers". We already know you like it, because you posted it. Ask your kids what they think of self-liking (but bear in mind, you are going to be laughed at)
-
In theory, you could write JQL that says "for yesterday, show me issues created between 10am and 11am". Then "for the day before yesterday, show me issues created between 10am and 11am". Then "for two days ago, show me issues created between 10am and 11am". But it is far too clunky and JQL queries have a character limit…
-
Ok, I know this is an old one, but I stumbled across it while I was looking for a related bookmark. A couple of years ago, Atlassian added a function. Try adding this to <jira-home>/jira-config.properties jira.view.issue.show.quicksubtask.when.no.subtasks=true and then restart. The properties file might not exist, it's…
-
It would be a better tip if I could have remembered what the heck the line actually was! Try adding this to <jira-home>/jira-config.properties jira.view.issue.show.quicksubtask.when.no.subtasks=true and then restart. The properties file might not exist, it's only created when you need to move away from the defaults. If you…
-
My instinct would be to reach for scripts and automation. When something needs doing, create an issue, then have scripts/automation to create a sub-task for each required step, assigned to different people, and closing the master issue when all complete. You could vary the sub-tasks by type of issue very easily.
-
If you are on Server Jira, you can stick a line into the jira config file in the home directory that forces the sub-task panel to appear (with the + link) even when there are no sub-tasks.