Comments
-
This works in postgresql: select id, pname, lead from project a inner join nodeassociation b on b.source_node_id = a.id and b.sink_node_entity = 'WorkflowScheme'; Note that it only returns the project information. It does not show which workflow scheme is associated with the project.
-
I don't think that your use case makes sense. You have a custom Field "CFX". CFX has a list of possible values. On Tickets 1, 2 and 3, CFX="A". On Ticket 4, CFX = "B". how does the value in CFX relate to users?
-
I'm not sure if this is the problem: The API states that it is only available to Connect Apps.
-
I haven't done it either, but it looks pretty straightforward. There is a REST API documented here. It is a PUT to /groups/{gid}/users/{uid} where you supply the Group ID and the User ID. You can use the HttpURLConnection class to create the connection and execute the PUT statement.
-
Open the Services app (Windows+R services.msc). If you see Atlassian Jira and it is running, then you know that it is installed and running as a service. If you see Atlassian Jira and it is not running, but Jira is still working, then it is installed as a service, but has been started manually (using start.bat). If Jira is…
-
I am not aware of any plugin that will do this for you (which doesn't mean that there isn't) Is this an on-premise AD or Azure AD? Either way, you could use ScriptRunner in a post-function transition to update the directory. If it is a local AD, I would create a PowerShell script and use ScriptRunner to call that script…
-
There is the capability to pop up an information dialog from ScriptRunner. It is contained in the com.onresolve.scriptrunner.runner.util.UserMessageUtil class. Unfortunately, this is not really documented anywhere. It would be great if Adaptavist would document the utility classes that are available. I am not aware of…
-
Your response was spot on. I modified the script to create a new list of admins using the original list as input and it works as expected. I appreciate the help. For anyone who wants to see the correct solution import com.atlassian.jira.component.ComponentAccessor; import com.atlassian.jira.security.groups.GroupManager;…
-
This is where Portfolio for Jira shines. You create the individual projects in Jira and then let Portfolio show how they roll up into a higher-level roadmap. It lets you do capacity planning and what-if projections. You should definitely consider using Portfolio for Jira to address this. If you want to stay entirely within…
-
To support multiple applications like this, you should look at Crowd. It will simplify the management of your various user domains. In addition, you will need plugins to accomplish what you want to do, which means that you may require a plugin for every application. Crowd will centralize all of this for you. Crowd natively…
-
Crowd creates a single User/Group directory allowing you to manage your users in a single place. This is especially useful if you combine multiple directories to create a single view of all of your users. Crowd will synch all of the users and groups to the applications you have connected to it. What these users and groups…
-
Getting Atlassian involved is your best call. My guess is that there is a misconfiguration that only they can correct.
-
Where does the SSO login link direct them? That would help track down where it is coming from.
-
The errors are all static checking errors, which can be ignored. You do need to define "issue" since the code assumes that this variable will be supplied by the caller. If you are going to use ScriptRunner, there is a better way to bring in the Insight code: import com.onresolve.scriptrunner.runner.customisers.WithPlugin…
-
There are differences between Insight's script console and ScriptRunner's console. They don't use the same groovy class and they set up the script environment slightly differently. In fact, there appears to be (or have been) a difference between the script console and the automation script runner. This has bitten me in the…
-
The script isn't correct. This should work for you: def formComponent = getFieldById(getFieldChanged()) def formBundle = getFieldByName("Bundle Version") List componentFieldValues = formComponent.getValue().collect {it.getName()} if ("NetSuite" in componentFieldValues) { formBundle.setHidden(false)…
-
You need to put this script on the Component/s field. You want the behavior to trigger when the component/s field is updated. That will then update the bundle version field.
-
I don't believe that there is any way to disable Basic Auth. Both Basic and OAUTH are always available. Which one you use is up to you. You should be getting a 401 error with this call since you are not passing in any authentication information. The "os_authType=basic" is a meaningless parameter. The 403 error probably…
-
Where did you put your behaviour? If it is in the screen Initializer, then it only executes the first time that the screen is shown. If you put it into the Component/s field, it will run each time Component/s is accessed.
-
Go to admin.atlassian.com and your Organization page. Under Security, make sure that Single Signon isn't enabled. Is it possible that someone turned it on without your knowledge?
-
Are you executing this in the Insight Script Console? Can you provide the syntax errors that you see?
-
There is no charge to use the Trello or Jira API.
-
You can use issue.property["key"] in a filter such as issue.property["request.channel.type"].value = portal to retrieve all of the JSD tickets submitted through the portal. Some plugins add properties or allow you to add your own properties to an issue.
-
Story Points is a field provided by Jira Software. It shows up under custom fields.
-
It seems to me that the source of your problem is that your branching strategy doesn't match your Jira workflow strategy. In my experience, we don't try to match Epics to branches. Epics are used to group stories for planning purposes but don't dictate branching strategy. If you want to match Epics to your branching…
-
You can delete your worklog. Would that solve your problem?
-
I want to understand your question better. The first paragraph says that you completed a release, merged it back to master and created a tag. I would expect that you would then delete that release branch. The second paragraph says that you merged master onto develop. At that point you can also branch from master to a new…
-
I'm not sure what your question is. Each story in your Sprint is or should be assigned a Story Points value. How you interpret Story Points is up to your team to decide. Best practice is to think of Story Points as an indication of implementation complexity, where 1 Story Point is a trivial task and 2 Story Points is a…
-
I am so used to working in Server that I forget the Cloud limitations, which are painful.
-
If you are using the JSD Automation facility, then you can specify either that it be run by the user who triggered the rule or by the project default. Those are you only two options. You might check out Automation Lite for Jira, which Atlassian just purchased and see if this will help you.