Issue.key Jira

0 views
Skip to first unread message

Lauro Pericles

unread,
Aug 5, 2024, 6:58:26 AM8/5/24
to prinreabocom
Ineed to get the current Issue key of the issue that the webpage is currently on so i can then use that to get to make a rest call to get a custom field value later on, So i decided to use the Context parameters to get the current issue key. on my console it will show the current issue but the request gives a 404 and my web panel wont load. When i take out the issueKey my webpanel will load fine, I am not sure how to get this to work your help will be greatly appreciated thank you in advanced. Below is my descriptor code

Not sure if that will fix your problem but your URL is kind of broken. You should pass the issue key either as a parameter /right-issue?issueKey=issue.key&foo=bar or as part of the path /right-issue/issue.key?foo=bar.


I've added a few automation rules to our project to send email on issue transition and I tried to include the issue's key within the email body by using the following syntax : $issue.key. But it's sending only $ to recipients.


In Chrome, you can do things like adding base url/secure/QuickSearch.jspa?searchString=%s with a key of "tracker" or whatever you call your Jira system (I have access to a lot, so I don't just use "Jira"), then Tracker BUG-1234 should go straight there.


For Firefox (and most others, but I only use Chrome and Firefox variants), it's a bit more clunky - you can add Atlassian applications as search engines, but the url bar will use the default, and you probably don't want to lose duckduckgo for default searches when you hit enter. A Jira search will appear in the bar beneath though, so "issue key + click on jira icon" will jump you straight to your issue.


Is there a way to map issue key when creating issues? I need to move my issues from one instance to another and I want to preserve the issue key (not just the issue ID). For example, AUTO-23 needs to remain number 23, and not reset back to AUTO-1.


It doesn't care what issue key you want, it imports issues in order, one line at a time (top to bottom through your csv), and uses the same logic that "click create, get issue" does when numbering - it takes the next one.


There is no "solution" beyond what I posted before. You have to create your import file in a specific order and fill in any blanks, and accept that importing into a project means that you have to have issue keys that match the project-sequence that Jira works with.


Thanks all! I got it. You do need to do the import through the Administration > System menu, not at the project level. If you're creating through project import, it will not allow issue key to be mapped. However, if you're a jira admin, you can override the mapping and select issuekey as many have indicated via screenshots above.


Update: it's because I wasn't logged in through the systems permission - I was only in automation from the project menu. You have to be logged in as an administrator and access the import option from the System menu, in order to use system fields.


We are wanting to use Confluence to post our roadmap to our customers using the jira macro. The issue is the jira macro displays links that I don't want exposed because our customers do not have access.


A separate post suggested creating custom fields for key and summary and displaying these instead. I am giving this a try, but I'm struggling to setup an automation rule. I don't want this to be a manual copy for every ticket. I am trying to copy the issue key and summary to custom fields when the ticket is created.


In case anyone finds this post while asking the same question I originally had, I realized that if I copy the issue key to a custom field, Confluence will still display it as a link. It will work as needed (no link) if I only put in the number (what follows after the project abbreviation and dash) but I have not found a way to do that just yet.


I got a requirement where the service desk tickets: Incidents/Service Requests/Problem, would carry its own issue key. For example an incident ticket will have INC-123; and a service request ticket will have SR-124 and so on. And all tickets in just one project.


I created a custom field to store "INC" or "SR" or "PB" based on issue type. Then I created an automation with IF/ELSE conditions when issue is created. The automation is to add a suffix on the Summary field as "PRJ-123INC-Short summary of incident". Where:

- PRJ is the project key

- 123 is the key sequence number

- INC stands for incident

- and the rest is the text in Summary field.


But the business wanted to have PRJ to be replaced with INC in the Summary field. What will be the smart value to extract the numbers in the issue key and prefix it with the custom field I created? I gone as far as... customfield_10221-((issue.key}} , but this also takes the PRJ part.

3a8082e126
Reply all
Reply to author
Forward
0 new messages