![]() What just happened? The screenshot above shows the remote user commenting on the issue, in context. ![]() Now, going back to the Test Case, imagine the remote user received that notification and replies, this can be mocked by using the same JEMH Test Case as earlier, just add the created issue KEY to the subject of the email before sending. Opening the Notification History tab will show the conversation of the issue (which will be blank as the issue was just created):Īdding a comment to the issue through the UI: Note in the created issue, the new Notification History Issue Tab: Starting with a JEMH Test Case (see Create a Test Case), just run an example to create an issue, set with whatever inbound address is required for your Profile.Īfter running the Test Case the results should be successful, e.g.: the definition of the Project and Notification History storage, changes to one will affect the other.Įdit the JIRA notification configuration by clicking on the pen icon, and select a notification scheme, as well as the events required to be notified:Īfter saving the JIRA notification configuration you will see:Īt this point, the JEMH Event Listener is fully primed to issue notifications to non-JIRA and JIRA users and to collect the notification traffic that is needed for the Notification History, all that remains is to create some traffic. #JIRA WIKI TAB UPDATE#Putting the JIRA issue name in the SVN commit message will update the subversion tab under the issue.When a Event Listener Project Configuration is created, some values are shared between JIRA and non-JIRA notifications, e.g. Creating a ticket:ĭon't mix labels with components! Components are automatically associated with a responsible person 'component lead', so they get updates if the component is mentioned. Label for tools and tidbits: kb-how-to-article JIRAĬonfigure your dashboard to show only the cases of interest: Dashboard → Name, Configure, share with en-sti-mta-CERN-ONLYĪdd Gadgets, fitlers, etc. TODO Our Wiki space should host all Projects under the LabVIEW applications node with their User Documentation. TODO How to open up our Wiki pages to other CERN users so they can read and possibly edit their specific project documentation? Should the documentation be hosted by us or by them? Distinguish Developer Documentation (for us) from User Documentation (for them).Īdd your project name as a label to the wiki page TODO Official RADE documentation should go on the Drupal webpage. You can include the development status of your projects in your documentation.Ĭonfluence cannot link to videos from external sources except YouTube and Vimeo You can, however, upload a video directly to the Wiki ( only if it's small! <25 MB) or better: Link it from the 'unlimited' RADE EOS storage space.īe careful when deleting pages (pages can be orphaned) JIRA plugin allows to include JIRA filters. #JIRA WIKI TAB HOW TO#Don Unknown User (fernanpa) fixed it! ^^ → How to add a VI Snippet to the WIKIįull support for HTML5 macros. There is a known bug in Google Chrome: draw.io does not resize grid or arrows properly. ![]() drawings with multiple sheets display first page by default, can go to second on fullscreenĬheck out Unknown User (dgomezdo)' flowcharts for good examples. Use labels on your documentation to to index pages for searching.ĭraw.io drawings can be easily inserted directly into the wiki by using the insertion (plus) icon. TODO We could rework the structure of the wiki a bit to be more ECE conform. Use the search box in the upper right corner to find stuff. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |