My backlog is starting to get incredibly long with some stories that are several years old. At first I was thinking of simply deleting them but then realized it was probably best not to do so for bookkeeping purposes and to have everything documented. As such, I was wondering if there is a way to create an "old"/"junk" folder where I can move old stories in the backlog that are most likely not relevant (but I don't want to completely lose visibility of). Any advice on how to do so would be much appreciated.
Hi Gareth,
Yes, take a look at this documentation for details: https://confluence.atlassian.com/display/AOD/Integrating+JIRA+OnDemand+with+Stash
Thanks Pedro, it doesn't work though. I can access Stash through an Apache instance via SSL now no problems, but when I try to add an application link from our instance of Stash to the OnDemand instance of JIRA I just get a timeout error.
If I try to make the application link the other way, from JIRA to Stash it completes the Incoming Authentication part ok, with a status of Configured. However the outgoing authentication section status is: Not Configured and the button labelled 'Enable' does not do anything.
Looking at the Outgoing Authentication section on the Stash instance now says this:
Please note that to configure Trusted Applications, Basic, or CORS authentication, you need to be a system administrator on the 'XXXXX JIRA' application. We recommend that you use OAuth for Application Link authentication.
Even though I am the administrator on our JIRA Ondemand instance, I am not a system-administrator, so it looks like this can't actually work.
Is this a known problem?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.