Comments
-
My guess is that Flow is using the Jira REST API for this, you'll need to set it up to use the REST calls that can extract user information from Jira as well as the issues.
-
You can give people permission to comment without needing to give them the rights to create or edit pages.
-
No, changing permissions does not affect the data. Best way to think of it is that permissions are read only when looking to see if someone can do something. They don't go onto issues, and the history of permissions has no effect on what you're doing now.
-
Eep! Sorry. I asked Kristian but got distracted and forgot to post back here! There are no rest APIs for enhanced search. But, you can make a rest call to a standard Jira filter which is created when they save an enhanced search filter as this will have the issues returned by the enhanced search filter in it.
-
Have a look at the workflow - in the transitions, look for the post-functions, you will find they all have a post-function for "fire event" - that's what you'll need your listener to listen for!
-
Yes, see https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/
-
Yes, see the announcement at https://community.atlassian.com/t5/Confluence-articles/Security-Advisory-for-Confluence-Server-and-Data-Center-August/ba-p/1787026
-
It looks like Atlassian have dropped the old mindville servers from when they acquired Insight, and not relocated the documentation in a visible place yet. We'll need Atlassian to get the servers back up, or give us a new place they've moved the docs to. I'll go ask :-)
-
I think this chunk of code should get you most of the way there: #foreach ( $label in $content.getLabels() ) #if ( ( $label == "Penguin" ) ) Penguins are here! #end #end
-
Start with https://support.atlassian.com/jira-cloud-administration/resources/ - there seems to be a lot there, but that just reflects that Jira is powerful and has a lot of "main" settings.
-
Yes, this is what validators are for - https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-validators-with-custom-fields/
-
No, you have to do all the things that the installation process performs, you can't have it run part way through the installation. Yes, that does include the db connection and putting a licence key in the right places, but you also need to populate the rest of the tables in the database and set up a user and set the flags…
-
They will, where they are appropriate. Which reports are you finding them missing from? What are the reports for and why would sub-tasks be useful to include?
-
The short-text and unlimited-text fields are the only two you can do off-the-shelf What character limit are you looking for (and why? might help us a bit)
-
There's no simple answer to this one, and there are contexts about context, and a very long essay about how it has changed over the years. But in Jira 8 and above, Atlassian upgraded and revamped the indexing, which shortens the answer to "this is not a performance concern for people on 8+" You'll have run into performance…
-
I think you might be confusing "parameter" with "variable" here. A parameter (in computer speak) is a value you feed into a function or routine to give it some information to work with. It is not an output or result. It's not something you would change during a routine. I'm English, so bear with my strained analogy -…
-
It's a bit of a weak, and rather dull answer for me, for several reasons. First, I am very English. So there's an obvious answer - Tea. Clear favourite of the five broad types is black tea, and I do tend to pick up a lot of Nilgiri, Blue Lady, Yunnan or just simple Assam. I used to have a borderline dangerous coffee…
-
Ok, you are looking at the wrong thing. You still should not care about the changes. The clash in build numbers simply tells you that your upgrade went wrong and was not completed. It doesn't matter what the changes were, they've gone wrong. You'll need to go back to the backup of the previous version and either use that,…
-
For Server and DC, it is usually shown in the footer at the bottom of every page, but if that has been turned off, you can still always look to the top right for "help (?) -> About Confluence" in the menu bar near to your profile icon. You did select "Cloud" as your type though, and if that is true, then the answer is…
-
No. The point of Cloud is it is a service. Attachments stored on issues is one of the functions of that service. There's no point storing them elsewhere. Let's have another look at the question - why do you think you want the files held elsewhere? What problem are you trying to solve? (bear in mind you wouldn't be able to…
-
That is what "in" is for - try Status in ("To do", Backlog)
-
I don't think you are using what Martin typed then, you've removed something. The = in Martin's query is comparing ossuetype to story, but your error message says you've used = against a list. Try using exactly what Martin gave.
-
Welcome to the Atlassian Community! This is not really something you would ever want do with a parameter. A parameter is something that has been given to your code to tell it to do something. You're not supposed to ignore them, you might as well just not have parameters. But if you re-cast the requirement as "do something…
-
It doesn't, that's one of the reasons the attempt at equivalence is just so wrong.
-
What are you using on the devices to work with Jira? Is it one of the Jira mobile apps or a browser? Which one?
-
No, there's no frustration, I am sorry to have written it in a way that gave you that impression! You are right on the connector - it was developed to allow the systems to work together, I was just trying to explain how it does it, so you know where to look and what to question. For most of us, there are only two ways to…
-
No, I'm saying you either need to run the install properly, or provide a fully configured system with everything in place. You can't run a partly configured system - the installation routine only creates the config files *after* every part of the setup routine is complete.
-
There's no way to know what permissions the account has just by looking at its roles. It is probably that the role of "admin" gives them admin rights, but that's nothing to do with being an assignable user. Start with the permission scheme for the project - what people/roles/groups/etc does that name as "assignable users"?
-
No, there's no way to do this. What you can do is place users or groups into default roles, so when you create a new project, you find them jumping into the project roles automatically.
-
JQL finds issues, not sprint data. It doesn't even have anything to say about any results, the output of running a JQL query is a simple set of pointers to a set of issues. JQL such as "sprint = <sprint name>" might be the sort of query you want to start with. It's what you display it in that goes and fetches the values…