Automation rule to identify an item that was part of the sprint since the "start sprint"

[Sujitha.Krishnan]

Hello!

Requirement - Need to identify those items that were part of the sprint when the sprint started Vs the ones that were pulled in at some later point in time.

Approach - Trying to create an automation rule to add a label "SprintPlanning" ONLY to those items that are part of the sprint when we start the sprint. Want this rule to be triggered when the sprint starts.

The Rule that I created:

The error :

What am I doing wrong? Can someone please help?

Thanks in advance.

[Hubert Cross]

This still seems to be broken. We are moving to Okta for SSO and I cannot access the REST API through it during testing. Will Atlassian provide a solution other than adopting their specific Crowds SSO product?

[Ankit]

Hi Hubert,

Can you let me know how using Crowd can resolve this issue of API access? I am trying to create a solution for this issue of API access for users created through SSO on Jira Server.

[agzam]

I would love to find a way to make this https://github.com/Netflix-Skunkworks/go-jira work for non-cloud/private Jira, sitting behind Okta. If anyone knows how, please tell me.

[Deleted user]

If you’re working with semi-automatic processing, one way is to login with your browser, grab the jsessionid cookie, and include that same cookie in your api requests.

[Abhishek Sharma]

Thanks @Brant Schroeder

If I use Oauth, then JIRA will be the oauth provider, but it may not be the identity provider for the user who is trying to access JIRA resources.

As a end user, my access to jira is through Okta (or Google account), so when the app which is registered with jira prompts me to log into jira, will I be able to log in with my google account ?

It seems almost like two layers of oauth/saml authentication.  My app uses is registration with Jira (clientid/secret) to redirect the user to jira login. Jira uses its authentication trust with Okta (or Google) to further redirect for a Okta/Google login.

EndUser ---->Login----> MyApp ----Oauth----> Jira ----Oauth/SAML---->Okta(or Google)

Will this work ?

[Balaji Dommaraju]

Hi @Abhishek Sharma

I too searching work flow for same requirement but I no luck. Have you found any solution.

Is there any way to authenticate JIRA rest api by OKTA access token. 

[Carl Puerschner]

@Abhishek Sharma @Brant Schroeder - I, too, am looking to for a solution to this same problem.  Any progress or news that can be shared?

Thanks!

[Abhishek Sharma]

I have not found a solution to this yet. I did not dig much deeper after i last committed. If anyone finds a solution then please post it here.

[Brant Schroeder]

Abhishek,

  You will need to use OAuth when you make the rest API call.  We are in the process of implementing Okta and I have been looking into this.  I have not found any specific information about except in the developer area of JIRA.  

https://bitbucket.org/atlassian_tutorial/atlassian-oauth-examples?_ga=2.56014818.81522426.1539045600-188448510.1531496950

Example Code: https://bitbucket.org/atlassian_tutorial/atlassian-oauth-examples/src/0c6b54f6fefe996535fb0bdb87ad937e5ffc402d/java/src/main/java/com/atlassian/oauth/client/example/?at=default&_ga=2.56014818.81522426.1539045600-188448510.1531496950

https://developer.atlassian.com/server/jira/platform/oauth/

https://developer.atlassian.com/server/jira/platform/jira-rest-api-example-oauth-authentication-6291692/