As many of you already know, ScriptRunner Behaviors wouldn’t work on a create page like this (/secure/CreateIssue.jspa), which is the classic Jira create screen. Does anyone have a creative solution to work around this restriction? The objective here is to share a shorter URL with my end users for ticket creation that pre-populates the Project and the issue type, and thereafter the Scriptrunner behaviors kick in and do their magic.
Hello and Welcome to Atlassian Community @Madhusudhan Matrubai
Lets say i understand your request right, tricky part here is that direct URLs like /secure/CreateIssue.jspa bypass Forge UI Modifications, which is what Behaviours rely on.
One of workaround could be building a simple custom Forge app that uses Atlassian’s CreateIssueModal API. This allows you to launch the native create modal with your project and issue type pre-selected, ensuring Behaviours still trigger.
If a Forge app isn't an option, alternative is using standard Jira default field values / Automation, or having users use the standard + Create button.
Best,
Arek🤠
Hey Arkadiusz, Thanks for your reply. I'm curious to explore your suggestion, so I'll give that a try and see if it works, and keep you posted.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Madhusudhan Matrubai
Welcome to the Atlassian Community!
Before suggesting an alternative, could you clarify one thing?
Are your users opening the classic create page intentionally, or are you simply looking for a way to share a URL that pre-populates the Project and Issue Type before Behaviours are applied?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Gor, Thanks for your reply.
To answer your question, Nope, they are not opening the classic create page intentionally, it's just that I want to share a shorter URL for users to create tickets and that's the only way it's currently working. However, apart from populating the project name and issue type, I would still need the rest of the Behaviors to work, which currently it's not and hence looking for alternatives.
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.