[JIRA] (JENKINS-51095) after successfully importing job in destination folder, the success-prompt offers an invalid URL to visit

2019-01-16 Thread esc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Emilio Escobar  assigned an issue to Emilio Escobar   
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51095  
 
 
  after successfully importing job in destination folder, the success-prompt offers an invalid URL to visit   
 

  
 
 
 
 

 
Change By: 
 Emilio Escobar   
 
 
Assignee: 
 Emilio  Escobar   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51095) after successfully importing job in destination folder, the success-prompt offers an invalid URL to visit

2018-05-02 Thread gurce.isikyil...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gurce Isikyildiz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51095  
 
 
  after successfully importing job in destination folder, the success-prompt offers an invalid URL to visit   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2018-05-03-11-06-13-676.png  
 
 
Components: 
 job-import-plugin  
 
 
Created: 
 2018-05-03 01:09  
 
 
Environment: 
 windows  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Gurce Isikyildiz  
 

  
 
 
 
 

 
 In relation to JENKINS-23809 and the additional mechanism of specifying a destination folder to import to:   I recently made use of the job-import-plugin. It successfully imported my job to my desired destination folder, which I can attest to by visiting that destination folder manually.   However, just a minor issue that I noticed was that the SUCCESS notification given provided an incorrect url path that didn't take into account the destination path I provided. I'm guessing this was just a small oversight?